On Thu, Aug 27, 2015 at 9:30 AM, Eric Dumazet <eric.duma...@gmail.com> wrote: > On Thu, 2015-08-27 at 09:16 -0700, Michael Marineau wrote: > >> >> Oh, interesting. Looks like that patch didn't get CC'd to stable >> though, is there a reason for that or just oversight? > > We never CC stable for networking patches. > > David Miller prefers to take care of this himself.
Ah, right, sorry. forgot about that. :) > > ( this is in Documentation/networking/netdev-FAQ.txt ) > > Q: How can I tell what patches are queued up for backporting to the > various stable releases? > > A: Normally Greg Kroah-Hartman collects stable commits himself, but > for networking, Dave collects up patches he deems critical for the > networking subsystem, and then hands them off to Greg. > > There is a patchworks queue that you can see here: > http://patchwork.ozlabs.org/bundle/davem/stable/?state=* > > It contains the patches which Dave has selected, but not yet handed > off to Greg. If Greg already has the patch, then it will be here: > http://git.kernel.org/cgit/linux/kernel/git/stable/stable-queue.git > > A quick way to find whether the patch is in this stable-queue is > to simply clone the repo, and then git grep the mainline commit ID, e.g. > > stable-queue$ git grep -l 284041ef21fdf2e > releases/3.0.84/ipv6-fix-possible-crashes-in-ip6_cork_release.patch > releases/3.4.51/ipv6-fix-possible-crashes-in-ip6_cork_release.patch > releases/3.9.8/ipv6-fix-possible-crashes-in-ip6_cork_release.patch > stable/stable-queue$ > > > -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
