Lines Matching refs:be

6  - It must be obviously correct and tested.
7  - It cannot be bigger than 100 lines, with context.
9  - It must fix a real bug that bothers people (not a, "This could be a
16    be considered if they fix a notable performance or interactivity issue.
18    regression they should only be submitted by a distribution kernel
23    race can be exploited is also provided.
35  - Security patches should not be handled (solely) by the -stable review
44    in the sign-off area. Once the patch is merged it will be applied to
45    the stable tree without anything else needing to be done by the author
52    why you think it should be applied, and what kernel version you wish it to
53    be applied to.
60    it to be applied to.
69 (for example because it had to be backported) this must be very clearly
72 The upstream commit ID must be specified with a separate line above the commit
78 prerequisites which can be cherry-picked. This can be specified in the following
93 Also, some patches may have kernel version prerequisites.  This can be
108  - If accepted, the patch will be added to the -stable queue, for review by
114  - When the -stable maintainers decide for a review cycle, the patches will be
121    members did not realize, the patch will be dropped from the queue.
122  - At the end of the review cycle, the ACKed patches will be added to the
124  - Security patches will be accepted into the -stable tree directly from the
131    versions can be found at:
133  - The finalized and tagged releases of all stable kernels can be found