From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Helmut Schaa <helmut.schaa@googlemail.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: RT2870 failure in kernel 4.12.8
Date: Sat, 2 Sep 2017 10:22:24 +0200 [thread overview]
Message-ID: <20170902082223.GA11293@redhat.com> (raw)
In-Reply-To: <87y3pymqw2.fsf@purkki.adurom.net>
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
Thanks
Stanislaw
next prev parent reply other threads:[~2017-09-02 8:22 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 [this message]
2017-09-04 12:58 ` stable-kernel-rules: wireless and netdev-FAQ Kalle Valo
2017-09-01 2:06 ` RT2870 failure in kernel 4.12.8 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=20170902082223.GA11293@redhat.com \
--to=sgruszka@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=helmut.schaa@googlemail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@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).