linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Bjorn Helgaas <bhelgaas@google.com>,
	Taku Izumi <izumi.taku@jp.fujitsu.com>,
	Jiang Liu <jiang.liu@huawei.com>, x86 <x86@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-acpi@vger.kernel.org, Yinghai Lu <yinghai@kernel.org>
Subject: [PATCH part5 0/7] PCI, ACPI: pci root bus hotplug support - part5
Date: Sun,  2 Sep 2012 14:55:58 -0700	[thread overview]
Message-ID: <1346622965-30937-1-git-send-email-yinghai@kernel.org> (raw)

This part is to make sure ioapic and dmar handling sequence.

aka need to start driver for ioapic and dmar before regular pci device drivers.
and need to stop dmar and ioapic driver after pci device drivers.

user acpi_pci_driver to start and stop ioapic and dmar driver.

could get from
        git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git for-pci-root-bus-hotplug-part5


Jiang Liu (3):
  ACPI, PCI: Use normal list for struct acpi_pci_driver
  ACPI, PCI: Notify acpi_pci_drivers when hot-plugging PCI root bridges
  ACPI, PCI: Protect global lists in drivers/acpi/pci_root.c

Yinghai Lu (4):
  ACPI, PCI: Stop pci devices before acpi_pci_driver remove calling
  PCI: Set dev_node early for pci_dev
  PCI, x86: Move pci_enable_bridges() down
  ACPI, PCI: Skip extra pci_enable_bridges for non hot-add root

 drivers/acpi/pci_root.c    |  121 +++++++++++++++++++++++++++-----------------
 drivers/acpi/pci_root_hp.c |    1 +
 drivers/pci/probe.c        |    2 +
 drivers/pci/setup-bus.c    |    2 -
 include/acpi/acpi_bus.h    |    1 +
 include/linux/acpi.h       |    2 +-
 6 files changed, 79 insertions(+), 50 deletions(-)

-- 
1.7.7


             reply	other threads:[~2012-09-02 21:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-02 21:55 Yinghai Lu [this message]
2012-09-02 21:55 ` [PATCH part5 1/7] ACPI, PCI: Use normal list for struct acpi_pci_driver Yinghai Lu
2012-09-02 21:56 ` [PATCH part5 2/7] ACPI, PCI: Notify acpi_pci_drivers when hot-plugging PCI root bridges Yinghai Lu
2012-09-02 21:56 ` [PATCH part5 3/7] ACPI, PCI: Protect global lists in drivers/acpi/pci_root.c Yinghai Lu
2012-09-02 21:56 ` [PATCH part5 4/7] ACPI, PCI: Stop pci devices before acpi_pci_driver remove calling Yinghai Lu
2012-09-02 21:56 ` [PATCH part5 5/7] PCI: Set dev_node early for pci_dev Yinghai Lu
2012-09-02 21:56 ` [PATCH part5 6/7] PCI, x86: Move pci_enable_bridges() down Yinghai Lu
2012-09-02 21:56 ` [PATCH part5 7/7] ACPI, PCI: Skip extra pci_enable_bridges for non hot-add root Yinghai Lu

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=1346622965-30937-1-git-send-email-yinghai@kernel.org \
    --to=yinghai@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bhelgaas@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=izumi.taku@jp.fujitsu.com \
    --cc=jiang.liu@huawei.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).