From: "Bjørn Mork" <bjorn@mork.no>
To: Willy Tarreau <w@1wt.eu>
Cc: Scott Branden <sbranden@broadcom.com>,
Larry Finger <Larry.Finger@lwfinger.net>,
linux-wireless <linux-wireless@vger.kernel.org>,
Stable <stable@vger.kernel.org>, Andrew Kurn <kurn@sfu.ca>
Subject: Re: New USB ID 2001:3c25
Date: Wed, 03 Jun 2015 21:01:09 +0200 [thread overview]
Message-ID: <877frkfwga.fsf@nemi.mork.no> (raw)
In-Reply-To: <20150603175412.GA7362@1wt.eu> (Willy Tarreau's message of "Wed, 3 Jun 2015 19:54:12 +0200")
Willy Tarreau <w@1wt.eu> writes:
> On Wed, Jun 03, 2015 at 05:50:49PM +0000, Scott Branden wrote:
>> Hi Larry,
>>
>> There is no problem applying this patch to the stable tree.
>> I didn't know it was my responsibility to inform the stable mailing list every time a patch is accepted
>> in the latest kernel that could be applied to the stable tree?
>
> Just adding a Cc: stable@... in the commit message is enough to get it
> automatically queued once applied. Please check SubmittingPatches and
> stable_kernel_rules.txt for more information.
It isn't absolutely clear to me that those rules applies to "wireless",
being a sub-subsystem of "net". Quoting from stable_kernel_rules.txt :
"- If the patch covers files in net/ or drivers/net please follow netdev stable
submission guidelines as described in
Documentation/networking/netdev-FAQ.txt"
And the netdev-FAQ.txt goes into great detail describing the procedure,
which basically is "Give davem a hint that the patch should go to
stable". (and I'd like to note that this works very well in practice).
But I have noticed that some stable patches seem to flow more directly
into stable from "wireless" than from the rest of "net". I just don't
think the current _written_ docs support that procedure. Those docs
are possibly wrong? You should probably know much better than me :)
Bjørn
next prev parent reply other threads:[~2015-06-03 19:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 2:01 New USB ID 2001:3c25 Larry Finger
2015-06-03 17:50 ` Scott Branden
2015-06-03 17:54 ` Willy Tarreau
2015-06-03 19:01 ` Bjørn Mork [this message]
2015-06-03 21:52 ` Willy Tarreau
2015-06-03 17:58 ` Larry Finger
2015-06-04 10:38 ` Luis Henriques
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=877frkfwga.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=Larry.Finger@lwfinger.net \
--cc=kurn@sfu.ca \
--cc=linux-wireless@vger.kernel.org \
--cc=sbranden@broadcom.com \
--cc=stable@vger.kernel.org \
--cc=w@1wt.eu \
/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).