From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linuxfoundation.org ([140.211.169.12]:48875 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751980AbcJEHra (ORCPT ); Wed, 5 Oct 2016 03:47:30 -0400 Date: Wed, 5 Oct 2016 09:47:31 +0200 From: "gregkh@linuxfoundation.org" To: "Coelho, Luciano" Cc: "stable@vger.kernel.org" , "johannes@sipsolutions.net" , "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: <20161005074731.GA26585@kroah.com> References: <1475598165135166@kroah.com> <1475645890.4994.2.camel@sipsolutions.net> <20161005064758.GA9572@kroah.com> <1475651739.4904.8.camel@intel.com> <20161005072415.GA25372@kroah.com> <1475652901.4904.16.camel@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1475652901.4904.16.camel@intel.com> Sender: stable-owner@vger.kernel.org List-ID: 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