From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Coelho, Luciano" <luciano.coelho@intel.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
"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, 5 Oct 2016 09:47:31 +0200 [thread overview]
Message-ID: <20161005074731.GA26585@kroah.com> (raw)
In-Reply-To: <1475652901.4904.16.camel@intel.com>
On Wed, Oct 05, 2016 at 07:35:01AM +0000, Coelho, Luciano wrote:
> Anyway, this is probably a very rare case.
Yes it is, this is the first time it has come up in over a decade of
stable kernels that I can tell :)
> I was just nitpicking and thinking whether we could have prevented the
> (small) overhead of getting the patch in the stable queue, getting a
> comment and removing it from the queue, when we already knew from the
> beginning that it was irrelevant for some kernels.
A simple email like happened should be fine, it's easy to drop a patch
like I did. No need to micromanage the process for something that is so
rare...
thanks,
greg k-h
next prev parent reply other threads:[~2016-10-05 7:47 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
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 [this message]
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=20161005074731.GA26585@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=johannes@sipsolutions.net \
--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).