From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from kroah.org ([198.145.64.141]:33750 "EHLO coco.kroah.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751690Ab1B1RfF (ORCPT ); Mon, 28 Feb 2011 12:35:05 -0500 Date: Mon, 28 Feb 2011 09:36:04 -0800 From: Greg KH To: "Luis R. Rodriguez" Cc: Vivek Natarajan , Mohammed Shafi Shajakhan , linux-wireless@vger.kernel.org, stable@kernel.org Subject: Re: [stable] [stable 2.6.37][PATCH] ath9k: Fix ath9k to allow CPU to enter C3 state. Message-ID: <20110228173604.GA4375@kroah.com> References: <1298874054-3803-1-git-send-email-vnatarajan@atheros.com> <20110228142243.GB25724@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: linux-wireless-owner@vger.kernel.org List-ID: On Mon, Feb 28, 2011 at 09:21:01AM -0800, Luis R. Rodriguez wrote: > On Mon, Feb 28, 2011 at 9:20 AM, Luis R. Rodriguez wrote: > > On Mon, Feb 28, 2011 at 8:52 AM, Vivek Natarajan wrote: > >> On Mon, Feb 28, 2011 at 8:18 PM, Luis R. Rodriguez wrote: > >>> On Mon, Feb 28, 2011 at 6:22 AM, Greg KH wrote: > >>>> On Mon, Feb 28, 2011 at 11:50:53AM +0530, Vivek Natarajan wrote: > >>>>> The default qos value of 55 causes higher power consumption > >>>>> and the battery drains out quickly. So, remove the pm_qos request > >>>>> in the driver and the throughout issue in the Intel Pinetrail > >>>>> platforms in which the DMA latency is seen can be fixed with > >>>>> the following script: > >>>>> http://www.kernel.org/pub/linux/kernel/people/mcgrof/scripts/cpudmalatency.c > >>>>> http://johannes.sipsolutions.net/files/netlatency.c.txt > >>>>> > >>>>> More details can be found in the following bugzilla link: > >>>>> https://bugzilla.kernel.org/show_bug.cgi?id=27532 > >>>>> > >>>>> Cc: stable@kernel.org > >>>>> Signed-off-by: Mohammed Shafi Shajakhan > >>>>> Signed-off-by: Vivek Natarajan > >>>> > >>>> Why did you send me 3 copies of this patch, when I don't need any copies > >>>> of it? > >>>> > >>>> Totally confused, > >>> > >>> Vivek, please only ask John to send this to David as stable so it can > >>> get into 2.6.38-rc, then once there you can refer the sha1sum from > >>> Linus' tree and justify propagating into the stable series. > >>> > >> I had sent separate patches for v2.6.37 and for v2.6.38 since the > >> patch could not be applied directly to previous versions. So, should I > >> send this rebased patch for v2.6.37 only after it makes it into > >> v2.6.38? > > > > Affirmative. You cannot propagate stable patches unless they are > > already in Linus' tree. > > See: > > http://wireless.kernel.org/en/users/Documentation/Fix_Propagation And of course, the file, Documentation/stable_kernel_rules.txt thanks, greg k-h