From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linuxfoundation.org ([140.211.169.12]:47322 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751301AbcJEHYP (ORCPT ); Wed, 5 Oct 2016 03:24:15 -0400 Date: Wed, 5 Oct 2016 09:24:15 +0200 From: "gregkh@linuxfoundation.org" To: "Coelho, Luciano" Cc: "johannes@sipsolutions.net" , "stable@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: <20161005072415.GA25372@kroah.com> References: <1475598165135166@kroah.com> <1475645890.4994.2.camel@sipsolutions.net> <20161005064758.GA9572@kroah.com> <1475651739.4904.8.camel@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1475651739.4904.8.camel@intel.com> Sender: stable-owner@vger.kernel.org List-ID: On Wed, Oct 05, 2016 at 07:15:41AM +0000, Coelho, Luciano wrote: > On Wed, 2016-10-05 at 08:47 +0200, gregkh@linuxfoundation.org wrote: > > 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 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. > > Is there a way to mark the Fixes tag with the minimum kernel version as we would do e.g. with "Cc: stable@vger.kernel.org�# 4.8+"? The fixes tag is to show what commit it fixed. And since you were fixing a patch that is in the 4.7 release, you are implying that it is resolving an issue for that kernel, right? So just don't use the fixes: tag if that's not what you are really doing. thanks, greg k-h