From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Cc: linux-pci@vger.kernel.org,
linux acpi <linux-acpi@vger.kernel.org>,
Len Brown <lenb@kernel.org>, "Li, Shaohua" <shaohua.li@intel.com>
Subject: Re: [PATCH 0/5] pci-acpi: improvement for _OSC evaluation
Date: Fri, 16 May 2008 11:00:05 -0700 [thread overview]
Message-ID: <200805161100.06049.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <482BD572.30504@jp.fujitsu.com>
On Wednesday, May 14, 2008 11:17 pm Kenji Kaneshige wrote:
> Hi,
>
> Here are some improvement patches for _OSC evaluation on PCI.
>
> - [PATCH 1/5] pci-acpi: remove duplicate code for _OSC
> - [PATCH 2/5] pci-acpi: use local buffer for _OSC
> - [PATCH 3/5] pci-acpi: add flag to indicate query had been done
> - [PATCH 4/5] pci-acpi: remove unused variable in __pci_osc_support_set
> - [PATCH 5/5] pci-acpi: minor cleanups for _OSC
>
> For details, please see the header of each patch.
These cleanups look nice; Shaohua maybe you could take a look too and
ack/nack?
Thanks,
Jesse
next prev parent reply other threads:[~2008-05-16 18:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 6:17 [PATCH 0/5] pci-acpi: improvement for _OSC evaluation Kenji Kaneshige
2008-05-15 6:18 ` [PATCH 1/5] pci-acpi: remove duplicate code for _OSC Kenji Kaneshige
2008-05-15 6:20 ` [PATCH 2/5] pci-acpi: use local buffer " Kenji Kaneshige
2008-05-15 6:21 ` [PATCH 3/5] pci-acpi: add flag to indicate query had been done Kenji Kaneshige
2008-05-15 6:22 ` [PATCH 4/5] pci-acpi: remove unused variable in __pci_osc_support_set Kenji Kaneshige
2008-05-15 6:23 ` [PATCH 5/5] pci-acpi: minor cleanups for _OSC Kenji Kaneshige
2008-05-16 18:00 ` Jesse Barnes [this message]
2008-05-19 3:29 ` [PATCH 0/5] pci-acpi: improvement for _OSC evaluation Shaohua Li
2008-05-19 22:27 ` Jesse Barnes
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=200805161100.06049.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=shaohua.li@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox