Techwizz/kernel-fxtec-pro1x
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

[PATCH] Docs update: small fixes to stable_kernel_rules.txt

Browse source 
Small spelling, formating & similar fixes to stable_kernel_rules.txt

Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
This commit is contained in:
Jesper Juhl 2006-01-09 20:53:59 -08:00 committed by Linus Torvalds
parent 5dd94ed249
commit e48e99093c
1 changed files with 29 additions and 31 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

60
Documentation/stable_kernel_rules.txt
View file

@ -1,58 +1,56 @@
Everything you ever wanted to know about Linux 2.6 -stable releases. Everything you ever wanted to know about Linux 2.6 -stable releases.
Rules on what kind of patches are accepted, and what ones are not, into Rules on what kind of patches are accepted, and which ones are not, into the
the "-stable" tree: "-stable" tree:
- It must be obviously correct and tested. - It must be obviously correct and tested.
- It can not bigger than 100 lines, with context. - It can not be bigger than 100 lines, with context.
- It must fix only one thing. - It must fix only one thing.
- It must fix a real bug that bothers people (not a, "This could be a - It must fix a real bug that bothers people (not a, "This could be a
problem..." type thing.) problem..." type thing).
- It must fix a problem that causes a build error (but not for things - It must fix a problem that causes a build error (but not for things
marked CONFIG_BROKEN), an oops, a hang, data corruption, a real marked CONFIG_BROKEN), an oops, a hang, data corruption, a real
security issue, or some "oh, that's not good" issue. In short, security issue, or some "oh, that's not good" issue. In short, something
something critical. critical.
- No "theoretical race condition" issues, unless an explanation of how - No "theoretical race condition" issues, unless an explanation of how the
the race can be exploited. race can be exploited is also provided.
- It can not contain any "trivial" fixes in it (spelling changes, - It can not contain any "trivial" fixes in it (spelling changes,
whitespace cleanups, etc.) whitespace cleanups, etc).
- It must be accepted by the relevant subsystem maintainer. - It must be accepted by the relevant subsystem maintainer.
- It must follow Documentation/SubmittingPatches rules. - It must follow the Documentation/SubmittingPatches rules.
Procedure for submitting patches to the -stable tree: Procedure for submitting patches to the -stable tree:
- Send the patch, after verifying that it follows the above rules, to - Send the patch, after verifying that it follows the above rules, to
stable@kernel.org. stable@kernel.org.
- The sender will receive an ack when the patch has been accepted into - The sender will receive an ACK when the patch has been accepted into the
the queue, or a nak if the patch is rejected. This response might queue, or a NAK if the patch is rejected. This response might take a few
take a few days, according to the developer's schedules. days, according to the developer's schedules.
- If accepted, the patch will be added to the -stable queue, for review - If accepted, the patch will be added to the -stable queue, for review by
by other developers. other developers.
- Security patches should not be sent to this alias, but instead to the - Security patches should not be sent to this alias, but instead to the
documented security@kernel.org. documented security@kernel.org address.
Review cycle: Review cycle:
- When the -stable maintainers decide for a review cycle, the patches - When the -stable maintainers decide for a review cycle, the patches will be
will be sent to the review committee, and the maintainer of the sent to the review committee, and the maintainer of the affected area of
affected area of the patch (unless the submitter is the maintainer of the patch (unless the submitter is the maintainer of the area) and CC: to
the area) and CC: to the linux-kernel mailing list. the linux-kernel mailing list.
- The review committee has 48 hours in which to ack or nak the patch. - The review committee has 48 hours in which to ACK or NAK the patch.
- If the patch is rejected by a member of the committee, or linux-kernel - If the patch is rejected by a member of the committee, or linux-kernel
members object to the patch, bringing up issues that the maintainers members object to the patch, bringing up issues that the maintainers and
and members did not realize, the patch will be dropped from the members did not realize, the patch will be dropped from the queue.
queue. - At the end of the review cycle, the ACKed patches will be added to the
- At the end of the review cycle, the acked patches will be added to latest -stable release, and a new -stable release will happen.
the latest -stable release, and a new -stable release will happen. - Security patches will be accepted into the -stable tree directly from the
- Security patches will be accepted into the -stable tree directly from security kernel team, and not go through the normal review cycle.
the security kernel team, and not go through the normal review cycle.
Contact the kernel security team for more details on this procedure. Contact the kernel security team for more details on this procedure.
Review committe: Review committe:
- This will be made up of a number of kernel developers who have - This is made up of a number of kernel developers who have volunteered for
volunteered for this task, and a few that haven't. this task, and a few that haven't.