Lines Matching full:stable

134 Q: How can I tell what patches are queued up for backporting to the various stable releases?
136 A: Normally Greg Kroah-Hartman collects stable commits himself, but for
142   http://patchwork.ozlabs.org/bundle/davem/stable/?state=*
147   https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git
149 A quick way to find whether the patch is in this stable-queue is to
153   stable-queue$ git grep -l 284041ef21fdf2e
157   stable/stable-queue$
159 Q: I see a network patch and I think it should be backported to stable.
161 Q: Should I request it via stable@vger.kernel.org like the references in
162 the kernel's Documentation/process/stable-kernel-rules.rst file say?
163 A: No, not for networking.  Check the stable queues as per above first
165 listing the upstream commit ID and why you think it should be a stable
168 Before you jump to go do the above, do note that the normal stable rules
169 in :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`
176 mainline, the better the odds that it is an OK candidate for stable.  So
180 Q: I have created a network patch and I think it should be backported to stable.
182 Q: Should I add a Cc: stable@vger.kernel.org like the references in the
185 stable, then ensure you write a decent commit log that describes who
188 handled appropriately and most likely get put in the patchworks stable
192 stable that does *not* belong in the commit log, then use the three dash
197 Q: Are all networking bug fixes backported to all stable releases?
200 last two stable releases. For earlier stable releases, each stable
202 patch is missing from an earlier stable branch, please notify
203 stable@vger.kernel.org with either a commit ID or a formal patch