From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from mail.linuxfoundation.org ([140.211.169.12]:47013 "EHLO
        mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752005AbcJEGr5 (ORCPT
        <rfc822;stable@vger.kernel.org>); Wed, 5 Oct 2016 02:47:57 -0400
Date: Wed, 5 Oct 2016 08:47:58 +0200
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Coelho, Luciano" <luciano.coelho@intel.com>,
        "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
Message-ID: <20161005064758.GA9572@kroah.com>
References: <1475598165135166@kroah.com>
 <1475645890.4994.2.camel@sipsolutions.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <1475645890.4994.2.camel@sipsolutions.net>
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

On Wed, Oct 05, 2016 at 07:38:10AM +0200, Johannes Berg wrote:
> 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.

Ok, thanks for letting me know, I've now dropped it from the stable
queue.

greg k-h