From: Alex Chiang <achiang@hp.com>
To: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
linux acpi <linux-acpi@vger.kernel.org>,
Andrew Patterson <andrew.patterson@hp.com>
Subject: Re: [PATCH 1/2] PCI/ACPI: move _OSC code to pci_root.c
Date: Thu, 5 Feb 2009 08:49:36 -0700 [thread overview]
Message-ID: <20090205154936.GC24033@ldl.fc.hp.com> (raw)
In-Reply-To: <498AF557.4040601@jp.fujitsu.com>
Hi Kenji-san,
Sorry, I didn't read your patch in detail last time, and only saw
the one wording change that Andrew suggested.
Reading through now, I have a few more suggestions.
> + status = acpi_evaluate_object(handle, "_OSC", &input, &output);
> + if (ACPI_FAILURE(status))
> + return status;
> +
> + if (!output.length)
> + return AE_NULL_OBJECT;
> +
> + out_obj = output.pointer;
> + if (out_obj->type != ACPI_TYPE_BUFFER) {
> + printk(KERN_DEBUG "Evaluate _OSC returns wrong type\n");
"_OSC evaluation returned wrong type\n"
> + if (errors) {
> + if (errors & OSC_REQUEST_ERROR)
> + printk(KERN_DEBUG "_OSC request fails\n");
"_OSC request failed\n"
> + if (errors & OSC_INVALID_UUID_ERROR)
> + printk(KERN_DEBUG "_OSC invalid UUID\n");
> + if (errors & OSC_INVALID_REVISION_ERROR)
> + printk(KERN_DEBUG "_OSC invalid revision\n");
> + if (errors & OSC_CAPABILITIES_MASK_ERROR) {
> + if (capbuf[OSC_QUERY_TYPE] & OSC_QUERY_ENABLE)
> + goto out_success;
> + printk(KERN_DEBUG"Firmware did not grant requested "
> + "_OSC control\n");
I prefer to see this message on one line (and break the 80 column
rule) to make grepping easier. But this is a judgement call, and
I'll let you decide.
Thanks.
/ac
next prev parent reply other threads:[~2009-02-05 15:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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
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=20090205154936.GC24033@ldl.fc.hp.com \
--to=achiang@hp.com \
--cc=andrew.patterson@hp.com \
--cc=jbarnes@virtuousgeek.org \
--cc=kaneshige.kenji@jp.fujitsu.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox