linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: David Miller <davem@davemloft.net>
Cc: ian.kumlien@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4.20 000/111] 4.20.4-stable review
Date: Mon, 21 Jan 2019 20:21:48 +0100	[thread overview]
Message-ID: <20190121192148.GC4026@kroah.com> (raw)
In-Reply-To: <20190121.104824.1888946069199769292.davem@davemloft.net>

On Mon, Jan 21, 2019 at 10:48:24AM -0800, David Miller wrote:
> From: Ian Kumlien <ian.kumlien@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 <pabeni@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 <gregkh@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>`.

  reply	other threads:[~2019-01-21 19:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21 14:44 [PATCH 4.20 000/111] 4.20.4-stable review Ian Kumlien
2019-01-21 14:46 ` Greg KH
2019-01-21 14:56   ` Ian Kumlien
2019-01-21 15:10     ` Greg KH
2019-01-21 15:38       ` Ian Kumlien
2019-01-21 18:48         ` David Miller
2019-01-21 19:21           ` Greg KH [this message]
2019-01-21 19:43             ` David Miller
2019-01-21 19:27           ` Ian Kumlien
  -- strict thread matches above, loose matches on Subject: below --
2019-01-21 13:41 Greg Kroah-Hartman
2019-01-22 13:33 ` Naresh Kamboju
2019-01-22 16:44   ` Greg Kroah-Hartman
2019-01-22 19:24 ` Guenter Roeck
2019-01-23  6:43   ` Greg Kroah-Hartman
2019-01-22 22:25 ` shuah
2019-01-23  6:43   ` Greg Kroah-Hartman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190121192148.GC4026@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=davem@davemloft.net \
    --cc=ian.kumlien@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).