From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
linux acpi <linux-acpi@vger.kernel.org>,
Andrew Patterson <andrew.patterson@hp.com>,
Alex Chiang <achiang@hp.com>,
"Moore, Robert" <robert.moore@intel.com>
Subject: Re: [PATCH 1/2] PCI/ACPI: move _OSC code to pci_root.c
Date: Fri, 13 Feb 2009 13:24:31 -0800 [thread overview]
Message-ID: <200902131324.32281.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <498FD451.9070205@jp.fujitsu.com>
On Sunday, February 8, 2009 10:59 pm Kenji Kaneshige wrote:
> Move PCI _OSC management code from drivers/pci/pci-acpi.c to
> drivers/acpi/pci_root.c. The benefits are
>
> - We no longer need struct osc_data and its management code (contents
> are moved to struct acpi_pci_root). This simplify the code, and we
> no longer care about kmalloc() failure.
>
> - We can make pci_acpi_osc_support() be a static function, which is
> called only from drivers/acpi/pci_root.c.
>
> Signed-off-by: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
> Reviewed-by: Andrew Patterson <andrew.patterson@hp.com>
> Tested-by: Andrew Patterson <andrew.patterson@hp.com>
Applied this series, thanks Kenji-san, Andrew & Alex.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2009-02-13 21:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 6:58 [PATCH 0/2] PCI/ACPI: move _OSC code to pci_root.c (v.3) Kenji Kaneshige
2009-02-09 6:59 ` [PATCH 1/2] PCI/ACPI: move _OSC code to pci_root.c Kenji Kaneshige
2009-02-09 15:38 ` Alex Chiang
2009-02-13 21:24 ` Jesse Barnes [this message]
2009-02-09 7:00 ` [PATCH 2/2] PCI/ACPI: rename pci_osc_control_set() Kenji Kaneshige
-- strict thread matches above, loose matches on Subject: below --
2009-02-05 14:18 [PATCH 0/2] PCI/ACPI: move _OSC code to pci_root.c (v.2) Kenji Kaneshige
2009-02-05 14:19 ` [PATCH 1/2] PCI/ACPI: move _OSC code to pci_root.c Kenji Kaneshige
2009-02-05 15:49 ` Alex Chiang
2009-02-05 16:03 ` Moore, Robert
2009-02-06 5:43 ` Kenji Kaneshige
2009-02-06 16:14 ` Moore, Robert
2009-02-09 5:20 ` Kenji Kaneshige
2009-02-06 4:30 ` Kenji Kaneshige
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=200902131324.32281.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=achiang@hp.com \
--cc=andrew.patterson@hp.com \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox