From: Sasha Levin <sashal@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable <stable@vger.kernel.org>,
OpenWrt Development List <openwrt-devel@lists.openwrt.org>,
"David S . Miller" <davem@davemloft.net>,
Dave Taht <dave.taht@gmail.com>
Subject: Re: [PATCH v2] net: Allow class-e address assignment via ifconfig ioctl
Date: Sun, 17 Feb 2019 18:08:15 -0500 [thread overview]
Message-ID: <20190217230815.GP10616@sasha-vm> (raw)
In-Reply-To: <CACRpkdah9HEoXKqimsd-juvJrUq__-RObpR-WAwOF9FRaCdrLA@mail.gmail.com>
On Sun, Feb 17, 2019 at 10:18:29PM +0100, Linus Walleij wrote:
>On Sun, Feb 17, 2019 at 7:22 PM Sasha Levin <sashal@kernel.org> wrote:
>> Either way, David Miller will need to sign off on this since he manages
>> net/ -stable patches.
>
>I was unaware of different route points for stable patches, but it makes
>sense.
>
>Maybe we should add some kind of tagging
>entries to MAINTAINERS so it is clear where to route stable
>material? Right now I guess it is another one of these undocumented
>rules that one is supposed to pick up by first annoying everyone :D
>
>Are there other subsystems that have a second-level maintainer
>for stable, so I know before annoying someone else?
I really think that this is the only exception to the procees, and given
that David is only looking at the last 2 -stable releases (that would be
4.20 and 4.19 right now) it gets a bit tricky for folks who are not
intimate with the process. So no, you're not annoying anyone :)
FWIW, the process is documented here:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/networking/netdev-FAQ.rst#n134
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-02-17 23:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 13:16 [PATCH v2] net: Allow class-e address assignment via ifconfig ioctl Linus Walleij
2019-02-17 18:22 ` Sasha Levin
2019-02-17 21:18 ` Linus Walleij
2019-02-17 23:08 ` Sasha Levin [this message]
2019-02-17 21:49 ` David Miller
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=20190217230815.GP10616@sasha-vm \
--to=sashal@kernel.org \
--cc=dave.taht@gmail.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=openwrt-devel@lists.openwrt.org \
--cc=stable@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