From: Johannes Berg <johannes@sipsolutions.net>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"Coelho, Luciano" <luciano.coelho@intel.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"stable-commits@vger.kernel.org" <stable-commits@vger.kernel.org>
Subject: Re: Patch "iwlwifi: mvm: handle FRAME_RELEASE in MQ code" has been added to the 4.7-stable tree
Date: Wed, 05 Oct 2016 07:38:10 +0200 [thread overview]
Message-ID: <1475645890.4994.2.camel@sipsolutions.net> (raw)
In-Reply-To: <1475598165135166@kroah.com>
On Tue, 2016-10-04 at 16:22 +0000, gregkh@linuxfoundation.org wrote:
> This is a note to let you know that I've just added the patch titled
>
> iwlwifi: mvm: handle FRAME_RELEASE in MQ code
>
> to the 4.7-stable tree which can be found at:
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue
> .git;a=summary
>
> The filename of the patch is:
> iwlwifi-mvm-handle-frame_release-in-mq-code.patch
> and it can be found in the queue-4.7 subdirectory.
>
> If you, or anyone else, feels it should not be added to the stable
> tree, please let <stable@vger.kernel.org> know about it.
I have no particular objections to including this, but it only fixes
something for (unreleased) hardware that will likely never work on the
4.7 kernel (due to also unreleased firmware, and likelihood of never
releasing older firmware versions).
So there's almost certainly no point, but OTOH it also cannot possibly
hurt since this code path is only taken with that particular hardware.
johannes
next prev parent reply other threads:[~2016-10-05 5:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 16:22 Patch "iwlwifi: mvm: handle FRAME_RELEASE in MQ code" has been added to the 4.7-stable tree gregkh
2016-10-05 5:38 ` Johannes Berg [this message]
2016-10-05 6:47 ` gregkh
2016-10-05 7:15 ` Coelho, Luciano
2016-10-05 7:24 ` gregkh
2016-10-05 7:35 ` Coelho, Luciano
2016-10-05 7:47 ` gregkh
2016-10-05 7:51 ` Coelho, Luciano
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=1475645890.4994.2.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=gregkh@linuxfoundation.org \
--cc=luciano.coelho@intel.com \
--cc=stable-commits@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).