Lines Matching refs:it

6 (or not) into the mainline tree.  So it is the quality of this code which
30 before they will even review it.  A code base as large as the kernel
31 requires some uniformity of code to make it possible for developers to
32 quickly understand any part of it.  So there is no longer room for
48 on it for other reasons, but coding style changes should not be made for
54 80-column limit, for example), just do it.
69 in case somebody eventually needs to use the extra flexibility that it
72 never noticed - because it has never been used.  Or, when the need for
73 extra flexibility arises, it does not do so in a way which matches the
84 from another kernel subsystem, it is time to ask whether it would, in fact,
93 programmers, who see it as a way to efficiently encode a great deal of
95 use of it results in code which is much harder for others to read and
99 Conditional compilation with #ifdef is, indeed, a powerful feature, and it
136 placement of "inline" keywords may not just be excessive; it could also be
147 actually make it into the mainline until June, 2007 (2.6.22).  What
151 corporate doors.  But one large problem in particular was that it was not
154 retrofitted onto it.  
174 One final hazard worth mentioning is this: it can be tempting to make a
182 It is often argued that a regression can be justified if it causes things
183 to work for more people than it creates problems for.  Why not make a
184 change if it brings new functionality to ten systems for each one it
190 	progress at all. Is it two steps forwards, one step back, or one
196 user-space ABI.  Once an interface has been exported to user space, it must
213 not afflict a user later on, so it stands to reason that the automated
244  - DEBUG_SLAB can find a variety of memory allocation and use errors; it
288 flags is expected, and so on.  Sparse must be installed separately (it can
290 distributor does not package it); it can then be run on the code by adding
294 variety of potential coding problems; it can also propose fixes for those
364 "cleanup" needs a comment saying why it is done the way it is.  And so on.
373 or simply not using a specific functionality because it does not meet your
379 accompanied by a description of what the change is and why it is
388 say, this can be a large job, so it is best to be sure that the
398 not have to make life harder for out-of-tree developers than it needs to