All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Cc: linux acpi <linux-acpi@vger.kernel.org>,
	Andrew Patterson <andrew.patterson@hp.com>,
	Alex Chiang <achiang@hp.com>
Subject: [PATCH 0/2] PCI/ACPI: move _OSC code to pci_root.c (v.2)
Date: Thu, 05 Feb 2009 23:18:07 +0900	[thread overview]
Message-ID: <498AF51F.7070200@jp.fujitsu.com> (raw)

Hi,

Here are updated version (v.2) of "PCI/ACPI: move _OSC code to
pci_root.c" patches. Patches are

  - [PATCH 1/2] PCI/ACPI: move _OSC code to pci_root.c
  - [PATCH 2/2] PCI/ACPI: rename pci_osc_control_set()

ChangeLog
---------
[v.1 -> v.2]
  - Change the debug message.
    [old]: "_OSC FW not grant req. control."
    [new]: "Firmware did not grant requested _OSC control"
    (Based on the feedback from Andrew Patterson and Alex Chiang)

  - Rename pci_osc_control_set() to acpi_pci_osc_control_set() and
    move _OSC related definitions from include/linux/pci-acpi.h to
    include/linux/acpi.h.
    (Based on the feedback from Andrew Patterson)

Thanks,
Kenji Kaneshige


             reply	other threads:[~2009-02-05 14:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-05 14:18 Kenji Kaneshige [this message]
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
2009-02-05 14:19 ` [PATCH 2/2] PCI/ACPI: rename pci_osc_control_set() 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=498AF51F.7070200@jp.fujitsu.com \
    --to=kaneshige.kenji@jp.fujitsu.com \
    --cc=achiang@hp.com \
    --cc=andrew.patterson@hp.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    /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.