Lines Matching +full:s +full:- +full:merged

17 kernel community to ensure that your code is up to the kernel's quality
23 ----------------------
31  - If you have explained your patch well, reviewers will understand its
35    Many of the changes you may be asked to make - from coding style tweaks
36    to substantial rewrites - come from the understanding that Linux will
39  - Code review is hard work, and it is a relatively thankless occupation;
47  - Similarly, code reviewers are not trying to promote their employers'
54  - Be prepared for seemingly silly requests for coding style changes
112 -----------------
116 entry into a subsystem maintainer's tree.  How that works varies from one
118 things.  In particular, there may be more than one tree - one, perhaps,
120 longer-term work.
124 being -mm.  Patches which affect multiple subsystems can also end up going
125 through the -mm tree.
129 default.  Subsystem trees typically feed linux-next as well, making their
131 there's a good chance that you will get more comments from a new set of
137 burner so that the remaining patches can be worked into shape and merged.
141 blessings: before the advent of the linux-next tree, these conflicts often
146 merged into the mainline kernel.  Congratulations!  Once the celebration is
154 longer any question of your code being merged.  Resist that temptation,
171 well make it harder for you to get work merged in the future.
175 fix these bugs and ensure that your code's debut in a mainline kernel
177 the problems if at all possible.  That's what the stabilization period is
185 is insufficient motivation, though, it's also worth considering that the
187 after it's merged.  The next time you post a patch, they will be evaluating
193 -----------------------------
200 your own), or send an Acked-by: response back and let the original poster
213 chances are that one of the two patches will not be merged, and "mine was
215 somebody else's patch displaces yours and gets into the mainline, there is
217 get on with your work.  Having one's work shoved aside in this manner can
219 long after they have forgotten whose patch actually got merged.