From: Len Brown <lenb@kernel.org>
To: Andrew Patterson <andrew.patterson@hp.com>, robert.moore@intel.com
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
gregkh@suse.de, matthew@wil.cx, tom.l.nguyen@intel.com,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH 3/4] ACPI: Check for any matching CID when walking namespace.
Date: Wed, 23 Jan 2008 14:39:42 -0500 [thread overview]
Message-ID: <200801231439.42735.lenb@kernel.org> (raw)
In-Reply-To: <20080123001822.28190.3147.stgit@bluto.andrew>
Right Greg, this is not only an ACPI patch,
but a patch that touches the ACPICA core.
Lets get Bob to see if it applies to the latest upstream ACPICA code.
Andrew,
Do you give Intel permission to accept this patch under
both licenses on the top of the file, such that we can
re-distribute it in ACPICA to all the OSs that use ACPICA?
(hey, and check out the spiffy new acpica home page: http://acpica.org/ )
thanks,
-Len
On Tuesday 22 January 2008 19:18, Andrew Patterson wrote:
> From: Andrew Patterson <andrew.patterson@hp.com>
>
> The callback function acpi_ns_get_device_callback called from
> acpi_get_devices() will check CID's if the HID does not match. This code
> has a bug where it requires that all CIDs match the HID. Changed the code
> so that any CID match will do.
>
> Signed-off-by: Andrew Patterson <andrew.patterson@hp.com>
> ---
>
> drivers/acpi/namespace/nsxfeval.c | 11 ++++++++---
> 1 files changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/acpi/namespace/nsxfeval.c b/drivers/acpi/namespace/nsxfeval.c
> index f39fbc6..e562b24 100644
> --- a/drivers/acpi/namespace/nsxfeval.c
> +++ b/drivers/acpi/namespace/nsxfeval.c
> @@ -443,6 +443,7 @@ acpi_ns_get_device_callback(acpi_handle obj_handle,
> struct acpica_device_id hid;
> struct acpi_compatible_id_list *cid;
> acpi_native_uint i;
> + int found;
>
> status = acpi_ut_acquire_mutex(ACPI_MTX_NAMESPACE);
> if (ACPI_FAILURE(status)) {
> @@ -496,16 +497,20 @@ acpi_ns_get_device_callback(acpi_handle obj_handle,
>
> /* Walk the CID list */
>
> + found = 0;
> for (i = 0; i < cid->count; i++) {
> if (ACPI_STRNCMP(cid->id[i].value, info->hid,
> sizeof(struct
> - acpi_compatible_id)) !=
> + acpi_compatible_id)) ==
> 0) {
> - ACPI_FREE(cid);
> - return (AE_OK);
> + found = 1;
> + break;
> }
> }
> ACPI_FREE(cid);
> + if (!found) {
> + return (AE_OK);
> + }
> }
> }
>
>
next prev parent reply other threads:[~2008-01-23 19:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 0:18 [PATCH 0/4] ACPI fixes for PCIe AER Andrew Patterson
2008-01-23 0:18 ` [PATCH 1/4] PCI ACPI: Added a function to register _OSC with only PCIe devices Andrew Patterson
2008-01-23 0:18 ` [PATCH 2/4] PCI ACPI: AER driver should only register PCIe devices with _OSC Andrew Patterson
2008-01-23 0:18 ` [PATCH 3/4] ACPI: Check for any matching CID when walking namespace Andrew Patterson
2008-01-23 17:42 ` Greg KH
2008-01-23 19:35 ` Andrew Patterson
2008-01-23 19:39 ` Len Brown [this message]
2008-01-23 19:48 ` Andrew Patterson
2008-02-12 23:38 ` Moore, Robert
2008-01-23 0:18 ` [PATCH 4/4] PCI: Run ACPI _OSC method on root bridges only Andrew Patterson
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=200801231439.42735.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=andrew.patterson@hp.com \
--cc=gregkh@suse.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=robert.moore@intel.com \
--cc=tom.l.nguyen@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