linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
	Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	linux-pci@vger.kernel.org, linux-pm@lists.linux-foundation.org,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Len Brown <lenb@kernel.org>
Subject: Re: [PATCH 7/7] ACPI / PCI: Reorder checks in acpi_pci_osc_control_set()
Date: Mon, 02 Aug 2010 18:23:55 +0900	[thread overview]
Message-ID: <4C568EAB.5040600@jp.fujitsu.com> (raw)
In-Reply-To: <201007310037.36543.rjw@sisk.pl>

(2010/07/31 7:37), Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rjw@sisk.pl>
> 
> Make acpi_pci_osc_control_set() attempt to find the handle of the
> _OSC object under the given PCI root bridge object after verifying
> that its second argument is correct and that there is a struct
> acpi_pci_root object for the given root bridge handle.  This is
> more logical than the old code and it matches the code ordering
> in acpi_pci_root_osc_query().
> 
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> ---
>  drivers/acpi/pci_root.c |    8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> Index: linux-2.6/drivers/acpi/pci_root.c
> ===================================================================
> --- linux-2.6.orig/drivers/acpi/pci_root.c
> +++ linux-2.6/drivers/acpi/pci_root.c
> @@ -414,10 +414,6 @@ acpi_status acpi_pci_osc_control_set(acp
>  	acpi_handle tmp;
>  	struct acpi_pci_root *root;
>  
> -	status = acpi_get_handle(handle, "_OSC", &tmp);
> -	if (ACPI_FAILURE(status))
> -		return status;
> -
>  	control_req = (flags & OSC_PCI_CONTROL_MASKS);
>  	if (!control_req)
>  		return AE_TYPE;
> @@ -426,6 +422,10 @@ acpi_status acpi_pci_osc_control_set(acp
>  	if (!root)
>  		return AE_NOT_EXIST;
>  
> +	status = acpi_get_handle(handle, "_OSC", &tmp);
> +	if (ACPI_FAILURE(status))
> +		return status;
> +
>  	mutex_lock(&osc_lock);
>  	/* No need to evaluate _OSC if the control was already granted. */
>  	if ((root->osc_control_set & control_req) == control_req)
> 

Description is better than Kaneshige-san's [3/6].

And it seems that this patch can be applied alone too.

Reviewed-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>

      reply	other threads:[~2010-08-02  9:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-30 22:20 [PATCH 0/7] ACPI / PCI / PCIe: Rework _OSC handling Rafael J. Wysocki
2010-07-30 22:24 ` [PATCH 1/7] ACPI / PCI: Make acpi_pci_run_osc() use capbuf to return the result Rafael J. Wysocki
2010-08-02  9:16   ` Hidetoshi Seto
2010-08-02 14:12     ` Rafael J. Wysocki
2010-07-30 22:26 ` [PATCH 2/7] ACPI / PCI: Introduce acpi_pci_root_osc_query() Rafael J. Wysocki
2010-08-02  9:18   ` Hidetoshi Seto
2010-08-02 14:13     ` Rafael J. Wysocki
2010-07-30 22:32 ` [PATCH 3/7] PCI / PCIe: Ask BIOS for control of all native services at once (v5) Rafael J. Wysocki
2010-08-02  9:20   ` Hidetoshi Seto
2010-08-02 14:15     ` Rafael J. Wysocki
2010-07-30 22:34 ` [PATCH 4/7] PCI / PCIe: Disable PCIe port services during port initialization Rafael J. Wysocki
2010-08-02  9:21   ` Hidetoshi Seto
2010-07-30 22:35 ` [PATCH 5/7] PCI / PCIe: Remove the port driver module exit routine Rafael J. Wysocki
2010-08-02  9:21   ` Hidetoshi Seto
2010-08-02 14:18     ` Rafael J. Wysocki
2010-07-30 22:36 ` [PATCH 6/7] ACPI / PCI: Do not preserve _OSC control bits returned by a query Rafael J. Wysocki
2010-08-02  9:22   ` Hidetoshi Seto
2010-07-30 22:37 ` [PATCH 7/7] ACPI / PCI: Reorder checks in acpi_pci_osc_control_set() Rafael J. Wysocki
2010-08-02  9:23   ` Hidetoshi Seto [this message]

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=4C568EAB.5040600@jp.fujitsu.com \
    --to=seto.hidetoshi@jp.fujitsu.com \
    --cc=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=linux-pm@lists.linux-foundation.org \
    --cc=mjg59@srcf.ucam.org \
    --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;
as well as URLs for NNTP newsgroup(s).