Lines Matching refs:patch

62 As fixes make their way into the mainline, the patch rate will slow over
102 numbering scheme.  To be considered for an update release, a patch must (1)
134 process designed to ensure that each patch is reviewed for quality and that
135 each patch implements a change which is desirable to have in the mainline.
142 a patch gets into the kernel.  What follows below is an introduction which
146 The stages that a patch goes through are, generally:
148  - Design.  This is where the real requirements for the patch - and the way
156    process should turn up any major problems with a patch if all goes
159  - Wider review.  When the patch is getting close to ready for mainline
161    though this acceptance is not a guarantee that the patch will make it
162    all the way to the mainline.  The patch will show up in the maintainer's
164    process works, this step leads to more extensive review of the patch and
166    patch with work being done by others.
169    your patch may not be their highest priority.  If your patch is
172    patch has no review complaints but is not being merged by its
174    in updating the patch to the current kernel so that it applies cleanly
177  - Merging into the mainline.  Eventually, a successful patch will be
182  - Stable release.  The number of users potentially affected by the patch
205 developer could possibly inspect and select every patch unassisted.  The
215 patch for inclusion into the mainline kernel.
251 whether there are any conflicts to worry about; a patch which changes a
270 patch into the mainline, it is likely to end up in -mm.  Miscellaneous
276 The current -mm patch is available in the "mmotm" (-mm of the moment)
284 The primary tree for next-cycle patch merging is linux-next, maintained by
363 Quilt is a patch management system, rather than a source code management