Lines Matching refs:which

6 of conventions and procedures which are used in the posting of patches;
23 When posting code which is not yet considered ready for inclusion, it is a
25 which remains to be done and any known problems.  Fewer people will look at
26 patches which are known to be half-baked, but those who do will come in
32 There are a number of things which should be done before you consider
77 rules of thumb, however, which can help considerably:
82    split apart in ways which make sense.  The developers are interested in
90    should make a specific change which can be reviewed on its own and
99  - Each patch should yield a kernel which builds and runs properly; if your
107    to a single file as 500 separate patches - an act which did not make him
116    finger the last patch as the one which caused the problem, even though
117    the real bug is elsewhere.  Whenever possible, a patch which adds new
121 which takes quite a bit of time and thought after the "real work" has been
128 not done quite yet.  Each patch needs to be formatted into a message which
168 which introduced the bug if possible (and please provide both the commit ID
202    which can be found in Documentation/SubmittingPatches.  Code without a
216  - Reported-by: names a user who reported a problem which is fixed by this
234    which have had gratuitous white-space changes or line wrapping performed