view Documentation/stable_kernel_rules.txt @ 452:c7ed6fe5dca0

kexec: dont initialise regions in reserve_memory()

There is no need to initialise efi_memmap_res and boot_param_res in
reserve_memory() for the initial xen domain as it is done in
machine_kexec_setup_resources() using values from the kexec hypercall.

Signed-off-by: Simon Horman <horms@verge.net.au>
author Keir Fraser <keir.fraser@citrix.com>
date Thu Feb 28 10:55:18 2008 +0000 (2008-02-28)
parents 831230e53067
line source
1 Everything you ever wanted to know about Linux 2.6 -stable releases.
3 Rules on what kind of patches are accepted, and which ones are not, into the
4 "-stable" tree:
6 - It must be obviously correct and tested.
7 - It can not be bigger than 100 lines, with context.
8 - It must fix only one thing.
9 - It must fix a real bug that bothers people (not a, "This could be a
10 problem..." type thing).
11 - It must fix a problem that causes a build error (but not for things
12 marked CONFIG_BROKEN), an oops, a hang, data corruption, a real
13 security issue, or some "oh, that's not good" issue. In short, something
14 critical.
15 - No "theoretical race condition" issues, unless an explanation of how the
16 race can be exploited is also provided.
17 - It can not contain any "trivial" fixes in it (spelling changes,
18 whitespace cleanups, etc).
19 - It must be accepted by the relevant subsystem maintainer.
20 - It must follow the Documentation/SubmittingPatches rules.
23 Procedure for submitting patches to the -stable tree:
25 - Send the patch, after verifying that it follows the above rules, to
26 stable@kernel.org.
27 - The sender will receive an ACK when the patch has been accepted into the
28 queue, or a NAK if the patch is rejected. This response might take a few
29 days, according to the developer's schedules.
30 - If accepted, the patch will be added to the -stable queue, for review by
31 other developers.
32 - Security patches should not be sent to this alias, but instead to the
33 documented security@kernel.org address.
36 Review cycle:
38 - When the -stable maintainers decide for a review cycle, the patches will be
39 sent to the review committee, and the maintainer of the affected area of
40 the patch (unless the submitter is the maintainer of the area) and CC: to
41 the linux-kernel mailing list.
42 - The review committee has 48 hours in which to ACK or NAK the patch.
43 - If the patch is rejected by a member of the committee, or linux-kernel
44 members object to the patch, bringing up issues that the maintainers and
45 members did not realize, the patch will be dropped from the queue.
46 - At the end of the review cycle, the ACKed patches will be added to the
47 latest -stable release, and a new -stable release will happen.
48 - Security patches will be accepted into the -stable tree directly from the
49 security kernel team, and not go through the normal review cycle.
50 Contact the kernel security team for more details on this procedure.
53 Review committe:
55 - This is made up of a number of kernel developers who have volunteered for
56 this task, and a few that haven't.