renegade-project/linux-next
2
0
Fork 0
mirror of https://github.com/edk2-porting/linux-next.git synced 2024-12-17 01:34:00 +08:00
Code

Documentation/process/howto: Only send regression fixes after -rc1

Browse Source 
The original text was not clear if white space or other harmless patches
should be merged in -rc kernels.  The discussion at Kernel Summit said
that we should be more strict about sending regression fixes only.

Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
Dan Carpenter 2016-11-28 17:43:15 +03:00 committed by Jonathan Corbet
parent 9c240d7576
commit 388f9b20f9
1 changed files with 10 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
Documentation/process/howto.rst
View File

@ -267,15 +267,16 @@ process is as follows:
is using git (the kernel's source management tool, more information is using git (the kernel's source management tool, more information
can be found at https://git-scm.com/) but plain patches are also just can be found at https://git-scm.com/) but plain patches are also just
fine. fine.
- After two weeks a -rc1 kernel is released it is now possible to push - After two weeks a -rc1 kernel is released and the focus is on making the
only patches that do not include new features that could affect the new kernel as rock solid as possible. Most of the patches at this point
stability of the whole kernel. Please note that a whole new driver should fix a regression. Bugs that have always existed are not
(or filesystem) might be accepted after -rc1 because there is no regressions, so only push these kinds of fixes if they are important.
risk of causing regressions with such a change as long as the change Please note that a whole new driver (or filesystem) might be accepted
is self-contained and does not affect areas outside of the code that after -rc1 because there is no risk of causing regressions with such a
is being added. git can be used to send patches to Linus after -rc1 change as long as the change is self-contained and does not affect areas
is released, but the patches need to also be sent to a public outside of the code that is being added. git can be used to send
mailing list for review. patches to Linus after -rc1 is released, but the patches need to also be
sent to a public mailing list for review.
- A new -rc is released whenever Linus deems the current git tree to - A new -rc is released whenever Linus deems the current git tree to
be in a reasonably sane state adequate for testing. The goal is to be in a reasonably sane state adequate for testing. The goal is to
release a new -rc kernel every week. release a new -rc kernel every week.