Lines Matching refs:that

11 will shift toward doing things right and the tools which can help in that
20 Documentation/CodingStyle.  For much of that time, the policies described
21 in that file were taken as being, at most, advisory.  As a result, there is
23 style guidelines.  The presence of that code leads to two independent
26 The first of these is to believe that the kernel coding standards do not
27 matter and are not enforced.  The truth of the matter is that adding new
28 code to the kernel is very difficult if that code is not coded according to
29 the standard; many developers will request that the code be reformatted
41 The other trap is to assume that code which is already in the kernel is
63 But experience has shown that excessive or premature abstraction can be
68 always passed as zero by all callers.  One could retain that argument just
69 in case somebody eventually needs to use the extra flexibility that it
70 provides.  By that time, though, chances are good that the code which
85 make sense to pull out some of that code into a separate library or to
86 implement that functionality at a higher level.  There is no value in
126 that high; the creation of large numbers of inline functions is a classic
131 often does not apply to contemporary hardware.  Space *is* time, in that a
146 stack offered the promise of fixing that situation.  Yet, this code did not
151 corporate doors.  But one large problem in particular was that it was not
182 It is often argued that a regression can be justified if it causes things
207 For now, at least, the writing of error-free code remains an ideal that few
210 kernel.  To that end, the kernel developers have put together an impressive
213 not afflict a user later on, so it stands to reason that the automated
224 Note that not all compiler warnings are enabled by default.  Build the
259 ensure that locks are always acquired in the same order, that the same
270 fact of the matter, though, is that the resulting failure recovery paths
275 The kernel provides a fault injection framework which can do exactly that,
322 effects on performance, and anything else that might be needed to
323 understand the patch.  Be sure that the changelog says *why* the patch is
324 worth applying; a surprising number of developers fail to provide that
328 /proc files - should include documentation of that interface which enables
352 note that, often, comments are most notable by their absence.  Once again,
374 needs, that may be a sign that the API needs to change.  As a kernel
383 The other catch is that a developer who changes an internal API is
388 say, this can be a large job, so it is best to be sure that the
389 justification is solid.  Note that the Coccinelle tool can help with
393 ensure that code which has not been updated is caught by the compiler.
394 This will help you to be sure that you have found all in-tree uses of that
395 interface.  It will also alert developers of out-of-tree code that there is
396 a change that they need to respond to.  Supporting out-of-tree code is not
397 something that kernel developers need to be worried about, but we also do