From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org
Subject: [PATCH 0/5] PCI root bridge: get bus info from _CRS
Date: Thu, 18 Jun 2009 14:46:42 -0600 [thread overview]
Message-ID: <20090618203916.15850.7977.stgit@bob.kio> (raw)
The main patch in this series changes the way we discover the downstream bus
number of PCI root bridges. The end result should be the same as the current
code (as far as I know, this doesn't fix any bugs). But I believe this
follows the intent of the spec better, makes Linux work more like Windows,
and removes false accusations Linux makes against the BIOS.
---
Bjorn Helgaas (5):
ACPI: pci_root: remove unused dev/fn information
ACPI: pci_root: simplify list traversals
ACPI: pci_root: use driver data rather than list lookup
ACPI: pci_root: simplify acpi_pci_root_add() control flow
ACPI: pci_root: check _CRS, then _BBN for downstream bus number
drivers/acpi/pci_root.c | 185 ++++++++++++++---------------------------------
1 files changed, 57 insertions(+), 128 deletions(-)
next reply other threads:[~2009-06-18 20:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 20:46 Bjorn Helgaas [this message]
2009-06-18 20:46 ` [PATCH 1/5] ACPI: pci_root: check _CRS, then _BBN for downstream bus number Bjorn Helgaas
2009-06-19 3:35 ` Kenji Kaneshige
2009-06-18 20:46 ` [PATCH 2/5] ACPI: pci_root: simplify acpi_pci_root_add() control flow Bjorn Helgaas
2009-06-18 20:46 ` [PATCH 3/5] ACPI: pci_root: use driver data rather than list lookup Bjorn Helgaas
2009-06-18 20:47 ` [PATCH 4/5] ACPI: pci_root: simplify list traversals Bjorn Helgaas
2009-06-18 20:47 ` [PATCH 5/5] ACPI: pci_root: remove unused dev/fn information Bjorn Helgaas
2009-06-20 4:10 ` [PATCH 0/5] PCI root bridge: get bus info from _CRS Len Brown
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=20090618203916.15850.7977.stgit@bob.kio \
--to=bjorn.helgaas@hp.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@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