On Mon, Jan 21, 2019 at 10:48:24AM -0800, David Miller wrote: > From: Ian Kumlien <ian.kuml...@gmail.com> > Date: Mon, 21 Jan 2019 16:38:11 +0100 > > > Hi David, > > > > could we have your blessing to add the following patch to -stable for > > 4.20.4: > > commit 41d1c8839e5f8cb781cc635f12791decee8271b7 > > Author: Paolo Abeni <pab...@redhat.com> > > Date: Tue Jan 8 18:45:05 2019 +0100 > > > > net: clear skb->tstamp in bridge forwarding path > > It is already in my -stable queue: > > https://patchwork.ozlabs.org/bundle/davem/stable/?series=&submitter=&state=*&q=&archive= > > I honestly don't know why I bother putting forth such an effort to publish > what is in my -stable queue if people don't bother checking it. :-(
We should add a link to it in the stable_rules.rst file so that more people know to check it. Something like the patch below? thanks, greg k-h -------------------------- Subject: [PATCH] stable-kernel-rules.rst: add link to networking patch queue The networking maintainer keeps a public list of the patches being queued up for the next round of stable releases. Be sure to check there before asking for a patch to be applied so that you do not waste people's time. Signed-off-by: Greg Kroah-Hartman <gre...@linuxfoundation.org> diff --git a/Documentation/process/stable-kernel-rules.rst b/Documentation/process/stable-kernel-rules.rst index 0de6f6145cc6..7ba8cd567f84 100644 --- a/Documentation/process/stable-kernel-rules.rst +++ b/Documentation/process/stable-kernel-rules.rst @@ -38,6 +38,9 @@ Procedure for submitting patches to the -stable tree - If the patch covers files in net/ or drivers/net please follow netdev stable submission guidelines as described in :ref:`Documentation/networking/netdev-FAQ.rst <netdev-FAQ>` + after first checking the stable networking queue at + https://patchwork.ozlabs.org/bundle/davem/stable/?series=&submitter=&state=*&q=&archive= + to ensure the requested patch is not already queued up. - Security patches should not be handled (solely) by the -stable review process but should follow the procedures in :ref:`Documentation/admin-guide/security-bugs.rst <securitybugs>`.