Lines Matching refs:code

13 code.  You, as the author of that code, will be expected to work with the
14 kernel community to ensure that your code is up to the kernel's quality
22 developers as they review the code.  Working with reviewers can be, for
30    like to maintain a kernel with this code in it five or ten years later?
36    people remember who wrote kernel code, but there is little lasting fame
40    impulse to respond in kind.  Code review is about the code, not about
41    the people, and code reviewers are not attacking you personally.
43  - Similarly, code reviewers are not trying to promote their employers'
59 reviewers.  If you believe that the reviewer has misunderstood your code,
70 in a code change should result in an additional code comment instead; that
75 go away.  They will not go away.  If you repost code without having
79 Speaking of reposting code: please bear in mind that reviewers are not
80 going to remember all the details of the code you posted the last time
86 when they revisit your code.
142 longer any question of your code being merged.  Resist that temptation,
146 More importantly, though: inclusion into the mainline puts your code into
149 how many people will build your code into their kernels.  And, of course,
163 fix these bugs and ensure that your code's debut in a mainline kernel
174 development community remembers developers who lose interest in their code
183 a patch to your code.  That is one of the advantages of having your code
193 are opposed by the author and maintainer of the code, but it only goes so
196 kernel, nobody has absolute veto power over any code.  Except maybe Linus.