Lines Matching full:stable

147 Q: How can I tell what patches are queued up for backporting to the various stable releases?
149 A: Normally Greg Kroah-Hartman collects stable commits himself, but for
155   https://patchwork.kernel.org/bundle/netdev/stable/?state=*
160   https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git
162 A quick way to find whether the patch is in this stable-queue is to
166   stable-queue$ git grep -l 284041ef21fdf2e
170   stable/stable-queue$
172 Q: I see a network patch and I think it should be backported to stable.
174 Q: Should I request it via stable@vger.kernel.org like the references in
175 the kernel's Documentation/process/stable-kernel-rules.rst file say?
176 A: No, not for networking.  Check the stable queues as per above first
178 listing the upstream commit ID and why you think it should be a stable
181 Before you jump to go do the above, do note that the normal stable rules
182 in :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`
189 mainline, the better the odds that it is an OK candidate for stable.  So
193 Q: I have created a network patch and I think it should be backported to stable.
195 Q: Should I add a Cc: stable@vger.kernel.org like the references in the
198 stable, then ensure you write a decent commit log that describes who
201 handled appropriately and most likely get put in the patchworks stable
205 stable that does *not* belong in the commit log, then use the three dash
210 Q: Are all networking bug fixes backported to all stable releases?
213 last two stable releases. For earlier stable releases, each stable
215 patch is missing from an earlier stable branch, please notify
216 stable@vger.kernel.org with either a commit ID or a formal patch