From: Hauke Mehrtens <hauke@hauke-m.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux-pm mailing list <linux-pm@lists.linux-foundation.org>,
linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] ath9k: Do not use legacy PCI power management
Date: Mon, 20 Dec 2010 01:05:55 +0100 [thread overview]
Message-ID: <4D0E9DE3.8050100@hauke-m.de> (raw)
In-Reply-To: <201012200032.21704.rjw@sisk.pl>
On 12/20/2010 12:32 AM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rjw@sisk.pl>
>
> The ath9k driver uses legacy PCI power management (system suspend
> and resume) callbacks, so make it use struct dev_pm_ops callbacks and
> let the PCI subsystem handle all of the PCI-specific details of
> system power transitions.
>
> This change has been tested on Acer Ferrari One with the
> Atheros AR928X PCI Express network adapter (rev. 01).
>
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> ---
>
> Hi,
>
> This patch has been sent already once under a slightly different subject
> and with a different changelog. I'm not sure what happened to it that time,
> so here it goes again.
>
> I'm quite confident it doesn't break things and it simplifies the driver's
> suspend and resume routines quite a bit, so please apply.
>
> Thanks,
> Rafael
>
Hi Rafael,
Your patch was already applied (see commit
f0e94b479c987abef17eb18e5c8e0ed178d00cd4 in linux-next) or didn't I got
your problem?
Hauke
next prev parent reply other threads:[~2010-12-20 0:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 22:36 [PATCH] ath9k: Convert to new PCI PM framework Rafael J. Wysocki
2010-10-15 23:54 ` Luis R. Rodriguez
2010-10-16 20:02 ` Rafael J. Wysocki
2010-10-16 1:28 ` Paul Stewart
2010-10-16 19:52 ` Rafael J. Wysocki
2010-12-19 23:32 ` [PATCH] ath9k: Do not use legacy PCI power management Rafael J. Wysocki
2010-12-20 0:05 ` Hauke Mehrtens [this message]
2010-12-20 0:14 ` Rafael J. Wysocki
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=4D0E9DE3.8050100@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=ath9k-devel@lists.ath9k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=rjw@sisk.pl \
/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