From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Matthew Garrett <mjg@redhat.com>,
Linux PCI <linux-pci@vger.kernel.org>,
"Moore, Robert" <robert.moore@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>
Subject: Re: [PATCH 1/8] PCI PM: Add function for checking PME status of devices
Date: Tue, 23 Feb 2010 20:56:35 +0100 [thread overview]
Message-ID: <201002232056.35526.rjw__34489.2344474376$1266958867$gmane$org@sisk.pl> (raw)
In-Reply-To: <20100222162142.06095230@jbarnes-piketon>
On Tuesday 23 February 2010, Jesse Barnes wrote:
> On Wed, 17 Feb 2010 23:36:58 +0100
> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
>
> > From: Rafael J. Wysocki <rjw@sisk.pl>
> >
> > Add function pci_check_pme_status() that will check the PME status
> > bit of given device and clear it along with the PME enable bit. It
> > will be necessary for PCI run-time power management.
> >
> > Based on a patch from Shaohua Li <shaohua.li@intel.com>
> >
> > Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> > ---
>
> Applied this series and dropped the old patches, thanks Rafael.
Great, thanks Jesse.
next prev parent reply other threads:[~2010-02-23 19:56 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 22:35 [PATCH 0/8] PCI run-time PM support (rev. 4) Rafael J. Wysocki
2010-02-17 22:36 ` [PATCH 1/8] PCI PM: Add function for checking PME status of devices Rafael J. Wysocki
2010-02-23 0:21 ` Jesse Barnes
2010-02-23 0:21 ` Jesse Barnes
2010-02-23 19:56 ` Rafael J. Wysocki [this message]
2010-02-23 19:56 ` Rafael J. Wysocki
2010-02-17 22:36 ` Rafael J. Wysocki
2010-02-17 22:39 ` [PATCH 2/8] PCI PM: PCIe PME root port service driver (rev. 5) Rafael J. Wysocki
2010-02-17 22:39 ` Rafael J. Wysocki
2010-02-18 4:08 ` Kenji Kaneshige
2010-02-18 4:08 ` Kenji Kaneshige
2010-02-18 19:57 ` Rafael J. Wysocki
2010-02-18 19:57 ` Rafael J. Wysocki
2010-02-19 2:07 ` Kenji Kaneshige
2010-02-19 2:07 ` Kenji Kaneshige
2010-02-17 22:40 ` [PATCH 3/8] PCI PM: Make it possible to force using INTx for PCIe PME signaling Rafael J. Wysocki
2010-02-17 22:40 ` Rafael J. Wysocki
2010-02-17 22:41 ` [PATCH 4/8] ACPI: Use GPE reference counting to support shared GPEs Rafael J. Wysocki
2010-02-18 7:05 ` Jin Dongming
2010-02-18 20:01 ` Rafael J. Wysocki
2010-02-18 20:01 ` Rafael J. Wysocki
2010-02-19 7:24 ` Jin Dongming
2010-02-19 21:08 ` Rafael J. Wysocki
2010-02-19 21:08 ` Rafael J. Wysocki
2010-02-19 7:24 ` Jin Dongming
2010-02-18 7:05 ` Jin Dongming
2010-02-17 22:41 ` Rafael J. Wysocki
2010-02-17 22:41 ` [PATCH 5/8] ACPI / PM: Add more run-time wake-up fields (rev. 2) Rafael J. Wysocki
2010-02-17 22:41 ` Rafael J. Wysocki
2010-02-17 22:42 ` [PATCH 6/8] ACPI / ACPICA: Multiple system notify handlers per device Rafael J. Wysocki
2010-02-17 22:42 ` Rafael J. Wysocki
2010-02-17 22:44 ` [PATCH 7/8] PCI / ACPI / PM: Platform support for PCI PME wake-up (rev. 9) Rafael J. Wysocki
2010-02-17 22:44 ` Rafael J. Wysocki
2010-02-17 22:44 ` [PATCH 8/8] PCI PM: Run-time callbacks for PCI bus type (rev. 2) Rafael J. Wysocki
2010-02-17 22:44 ` 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='201002232056.35526.rjw__34489.2344474376$1266958867$gmane$org@sisk.pl' \
--to=rjw@sisk.pl \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mjg@redhat.com \
--cc=robert.moore@intel.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.