Lines Matching refs:kernel
15 - Serious issues as reported by a user of a distribution kernel may also
18 regression they should only be submitted by a distribution kernel
43 Cc: stable@vger.kernel.org
51 stable@vger.kernel.org containing the subject of the patch, the commit ID,
52 why you think it should be applied, and what kernel version you wish it to
58 stable@vger.kernel.org. You must note the upstream commit ID in the
59 changelog of your submission, as well as the kernel version you wish
66 to apply to an older kernel (e.g., if API's have changed in the meantime).
81 Cc: <stable@vger.kernel.org> # 3.3.x: a1f84a3: sched: Check for idle
82 Cc: <stable@vger.kernel.org> # 3.3.x: 1b9508f: sched: Rate-limit newidle
83 Cc: <stable@vger.kernel.org> # 3.3.x: fd21073: sched: Fix affinity logic
84 Cc: <stable@vger.kernel.org> # 3.3.x
93 Also, some patches may have kernel version prerequisites. This can be
96 Cc: <stable@vger.kernel.org> # 3.3.x-
117 the linux-kernel mailing list.
119 - If the patch is rejected by a member of the committee, or linux-kernel
125 security kernel team, and not go through the normal review cycle.
126 Contact the kernel security team for more details on this procedure.
132 http://git.kernel.org/?p=linux/kernel/git/stable/stable-queue.git
135 http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git
140 - This is made up of a number of kernel developers who have volunteered for