Lines Matching refs:patches

8 patches.  One of the biggest mistakes that even experienced kernel
10 posting patches indicates a transition into the next stage of the process,
19 prevent the inclusion of your patches into the mainline.
88 that your patches go nowhere.
119 dedicated to patches planned for the next merge window, and another for
122 For patches applying to areas for which there is no obvious subsystem tree
123 (memory management patches, for example), the default tree often ends up
137 burner so that the remaining patches can be worked into shape and merged.
139 developers and, possibly, moving some patches between trees to ensure that
178 for; you can start creating cool new patches once any problems with the old
205 acceptable to you.  There is a certain resistance to merging patches which
207 far.  If you are seen as needlessly blocking good work, those patches will
213 chances are that one of the two patches will not be merged, and "mine was