From: Kalle Valo <kvalo@codeaurora.org>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Helmut Schaa <helmut.schaa@googlemail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: stable-kernel-rules: wireless and netdev-FAQ
Date: Mon, 04 Sep 2017 15:58:15 +0300 [thread overview]
Message-ID: <87ziaaoc2g.fsf_-_@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20170902082223.GA11293@redhat.com> (Stanislaw Gruszka's message of "Sat, 2 Sep 2017 10:22:24 +0200")
(adding netdev and lkml)
Stanislaw Gruszka <sgruszka@redhat.com> writes:
> On Fri, Sep 01, 2017 at 05:31:57PM +0300, Kalle Valo wrote:
>> Stanislaw Gruszka <sgruszka@redhat.com> writes:
>>
>> > On Thu, Aug 31, 2017 at 10:33:28AM -0500, Larry Finger wrote:
>> >> Should the patch to wireless-drivers be annotated with a Stable reference so
>> >> that it is added to 4.12 and 4.13?
>> >
>> > According to Documentation/networking/netdev-FAQ.txt networking patches
>> > should not be marked cc:stable, instead a decent commit log should
>> > be written describing a bugfix. Which I believe it is done for
>> > this patch.
>>
>> But that's for net and net-next trees, not for wireless trees. With
>> wireless patches we use "Cc: stable@..." references.
>
> Oh, ok. I was confused by below part of
> Documentation/process/stable-kernel-rules.rst
> (because wireless drivers are located in drivers/net/)
>
> - If the patch covers files in net/ or drivers/net please follow netdev stable
> submission guidelines as described in
> Documentation/networking/netdev-FAQ.txt
Yeah, that's confusing and should be clarified that wireless follows
traditional stable process. IIRC bluetooth does the same so it's not
just wireless.
Any volunteers to fix it? :)
--
Kalle Valo
next prev parent reply other threads:[~2017-09-04 12:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 17:03 RT2870 failure in kernel 4.12.8 Larry Finger
2017-08-31 7:55 ` Stanislaw Gruszka
2017-08-31 8:25 ` Kalle Valo
2017-08-31 15:33 ` Larry Finger
2017-09-01 8:57 ` Stanislaw Gruszka
2017-09-01 14:31 ` Kalle Valo
2017-09-01 15:02 ` Larry Finger
2017-09-04 12:47 ` Kalle Valo
2017-09-02 8:22 ` Stanislaw Gruszka
2017-09-04 12:58 ` Kalle Valo [this message]
2017-09-01 2:06 ` Larry Finger
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=87ziaaoc2g.fsf_-_@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=Larry.Finger@lwfinger.net \
--cc=helmut.schaa@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sgruszka@redhat.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 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).