linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Mohammed Shafi <mshajakhan@atheros.com>,
	Mohammed Shajakhan <Mohammed.Shajakhan@atheros.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	stable@kernel.org, Luis Rodriguez <Luis.Rodriguez@atheros.com>
Subject: Re: [stable] [RFC] ath9k: Fix ath9k prevents CPU to enter C3 states
Date: Fri, 4 Mar 2011 13:37:13 -0800	[thread overview]
Message-ID: <20110304213713.GA31324@kroah.com> (raw)
In-Reply-To: <20110304133722.GA9866@tuxdriver.com>

On Fri, Mar 04, 2011 at 08:37:23AM -0500, John W. Linville wrote:
> On Fri, Mar 04, 2011 at 11:36:37AM +0530, Mohammed Shafi wrote:
> > On Wednesday 16 February 2011 10:35 AM, Mohammed Shafi wrote:
> > >On Tuesday 15 February 2011 09:42 PM, John W. Linville wrote:
> > >>Despite the [RFC], I am applying this.  I should have reverted all
> > >>of this three weeks ago...
> > John can you please push this to stable kernel ?
> 
> Stable folks, this is the commit in Linus's tree;
> 
> commit 0f5cd45960173ba5b36727decbb4a241cbd35ef9

Too bad this commit doesn't apply to the .37-stable tree :(

Can someone provide stable@kernel.org a backported version of this?

thanks,

greg k-h

  parent reply	other threads:[~2011-03-04 21:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-15 15:59 [RFC] ath9k: Fix ath9k prevents CPU to enter C3 states Mohammed Shafi Shajakhan
2011-02-15 16:12 ` John W. Linville
2011-02-16  5:05   ` Mohammed Shafi
2011-03-04  6:06     ` Mohammed Shafi
2011-03-04 13:37       ` John W. Linville
2011-03-04 14:26         ` Mohammed Shafi
2011-03-04 21:37         ` Greg KH [this message]
2011-03-04 22:00           ` [PATCH] " Thomas Bächler
2011-03-07  5:39             ` Mohammed Shafi
2011-03-07  5:44           ` [stable] [RFC] " Mohammed Shafi

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=20110304213713.GA31324@kroah.com \
    --to=greg@kroah.com \
    --cc=Luis.Rodriguez@atheros.com \
    --cc=Mohammed.Shajakhan@atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mshajakhan@atheros.com \
    --cc=stable@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).