All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Vivek Natarajan <vivek.natraj@gmail.com>,
	Mohammed Shafi Shajakhan <mshajakhan@atheros.com>,
	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.
Date: Mon, 28 Feb 2011 09:36:04 -0800	[thread overview]
Message-ID: <20110228173604.GA4375@kroah.com> (raw)
In-Reply-To: <AANLkTikxfjcStGND0SAqgCA+sZBEa0Xo_mf-ZGpsQrks@mail.gmail.com>

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 <mcgrof@gmail.com> wrote:
> > On Mon, Feb 28, 2011 at 8:52 AM, Vivek Natarajan <vivek.natraj@gmail.com> wrote:
> >> On Mon, Feb 28, 2011 at 8:18 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> >>> On Mon, Feb 28, 2011 at 6:22 AM, Greg KH <greg@kroah.com> 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 <mshajakhan@atheros.com>
> >>>>> Signed-off-by: Vivek Natarajan <vnatarajan@atheros.com>
> >>>>
> >>>> 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

      reply	other threads:[~2011-02-28 17:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28  6:20 [stable 2.6.37][PATCH] ath9k: Fix ath9k to allow CPU to enter C3 state Vivek Natarajan
2011-02-28  6:20 ` [stable 2.6.38][PATCH] " Vivek Natarajan
2011-02-28 14:22 ` [stable] [stable 2.6.37][PATCH] " Greg KH
2011-02-28 14:48   ` Luis R. Rodriguez
2011-02-28 16:52     ` Vivek Natarajan
2011-02-28 17:20       ` Luis R. Rodriguez
2011-02-28 17:21         ` Luis R. Rodriguez
2011-02-28 17:36           ` Greg KH [this message]

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=20110228173604.GA4375@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --cc=mshajakhan@atheros.com \
    --cc=stable@kernel.org \
    --cc=vivek.natraj@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.