From: Jakub Kicinski <kuba@kernel.org>
To: Vladimir Oltean <olteanv@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Vladimir Oltean <vladimir.oltean@nxp.com>,
netdev@vger.kernel.org, Woojung Huh <woojung.huh@microchip.com>,
Arun Ramadoss <arun.ramadoss@microchip.com>,
UNGLinuxDriver@microchip.com, Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Brian Hutchinson <b.hutchman@gmail.com>
Subject: Re: [PATCH v2 net] net: dsa: microchip: make learning configurable and keep it off while standalone
Date: Tue, 23 Aug 2022 15:01:13 -0700 [thread overview]
Message-ID: <20220823150113.22616755@kernel.org> (raw)
In-Reply-To: <20220823214253.wbzjdxgforuryxqp@skbuf>
On Wed, 24 Aug 2022 00:42:53 +0300 Vladimir Oltean wrote:
> On Tue, Aug 23, 2022 at 02:38:31PM -0700, Jakub Kicinski wrote:
> > > @maintainers: when should I submit the backports to "stable", for older
> > > trees?
> >
> > "when" as is how long after Thu PR or "when" as in under what
> > conditions?
>
> how long after the "net" pull request, yes.
> I'm a bit confused as to how patches from "net" reach the stable queue.
> If they do get there, I'm pretty confident that Greg or Sasha will send
> out an email about patches failing to apply to this and that stable
> branch, and I can reply to those with backports.
Adding Greg, cause I should probably know but I don't.
My understanding is that Greg and Sasha scan Linus's tree periodically
and everything with a Fixes tag is pretty much guaranteed to be
selected. Whether that's a hard guarantee IDK. Would be neat if it was
so we don't have to add the CC: stable lines.
Also not sure if it's preferred to wait for the failure notification
or you should pre-queue the backport as soon as it reaches Linus.
I vague recall someone saying to wait for the notification...
next prev parent reply other threads:[~2022-08-23 22:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 16:48 [PATCH v2 net] net: dsa: microchip: make learning configurable and keep it off while standalone Vladimir Oltean
2022-08-18 18:12 ` Andrew Lunn
2022-08-23 21:38 ` Jakub Kicinski
2022-08-23 21:42 ` Vladimir Oltean
2022-08-23 22:01 ` Jakub Kicinski [this message]
2022-08-24 6:17 ` Greg Kroah-Hartman
2022-08-23 21:50 ` patchwork-bot+netdevbpf
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=20220823150113.22616755@kernel.org \
--to=kuba@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=arun.ramadoss@microchip.com \
--cc=b.hutchman@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.com \
--cc=woojung.huh@microchip.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.