From: Greg KH <greg@kroah.com>
To: Vivek Natarajan <vnatarajan@Atheros.com>
Cc: 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 06:22:43 -0800 [thread overview]
Message-ID: <20110228142243.GB25724@kroah.com> (raw)
In-Reply-To: <1298874054-3803-1-git-send-email-vnatarajan@atheros.com>
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,
greg k-h
next prev parent reply other threads:[~2011-02-28 14:23 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 ` Greg KH [this message]
2011-02-28 14:48 ` [stable] [stable 2.6.37][PATCH] " 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
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=20110228142243.GB25724@kroah.com \
--to=greg@kroah.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mshajakhan@Atheros.com \
--cc=stable@kernel.org \
--cc=vnatarajan@Atheros.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 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).