From: Jesse Barnes <jesse.barnes@intel.com>
To: Alex Chiang <achiang@hp.com>
Cc: lenb@kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH v3 2/2] PCI Hotplug: acpiphp: get pci_bus from acpi handle correctly
Date: Fri, 24 Jul 2009 14:38:27 -0700 [thread overview]
Message-ID: <20090724143827.31b4c37d@jbarnes-g45> (raw)
In-Reply-To: <20090723230305.4247.81288.stgit@bob.kio>
On Thu, 23 Jul 2009 17:03:05 -0600
Alex Chiang <achiang@hp.com> wrote:
> We cannot simply call acpi_get_pci_dev() on any random ACPI handle
> and hope that it works, because a PCI root bridge may not have
> an associated struct pci_dev.
>
> This is allowed per the PCI specification, and is referred to as a
> non-materialized bridge.
>
> So, depending on the type of PCI bridge that the handle points to,
> use the appropriate interface to return the struct pci_bus correctly.
>
> Signed-off-by: Alex Chiang <achiang@hp.com>
> ---
I put these in my linux-next branch, just because I'm really
conservative about the current release.
If we hear of boxes in the wild getting bitten by the non-materialized
bit, we can push this set back to stable.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2009-07-24 21:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 23:02 [PATCH v3 0/2] export acpi_pci_root to find pci_bus correctly Alex Chiang
2009-07-23 23:03 ` [PATCH v3 1/2] ACPI: export acpi_pci_root and friends Alex Chiang
2009-07-24 16:35 ` Bjorn Helgaas
2009-07-23 23:03 ` [PATCH v3 2/2] PCI Hotplug: acpiphp: get pci_bus from acpi handle correctly Alex Chiang
2009-07-24 16:35 ` Bjorn Helgaas
2009-07-24 21:38 ` Jesse Barnes [this message]
2009-07-24 23:58 ` Alex Chiang
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=20090724143827.31b4c37d@jbarnes-g45 \
--to=jesse.barnes@intel.com \
--cc=achiang@hp.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®