From: Greg KH <greg@kroah.com>
To: Andrew Patterson <andrew.patterson@hp.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
lenb@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 09:42:53 -0800 [thread overview]
Message-ID: <20080123174253.GA10387@kroah.com> (raw)
In-Reply-To: <20080123001822.28190.3147.stgit@bluto.andrew>
On Tue, Jan 22, 2008 at 05:18:22PM -0700, 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(-)
This should probably go through the ACPI tree, not the PCI tree, right?
thanks,
greg k-h
next prev parent reply other threads:[~2008-01-23 17:51 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 [this message]
2008-01-23 19:35 ` Andrew Patterson
2008-01-23 19:39 ` Len Brown
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=20080123174253.GA10387@kroah.com \
--to=greg@kroah.com \
--cc=andrew.patterson@hp.com \
--cc=gregkh@suse.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
--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