[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3459136.QID0qrXQHt@vostro.rjw.lan>
Date: Wed, 06 Feb 2013 23:05:14 +0100
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Yinghai Lu <yinghai@...nel.org>,
Myron Stowe <myron.stowe@...il.com>
Cc: Bjorn Helgaas <bhelgaas@...gle.com>,
Jiang Liu <jiang.liu@...wei.com>,
Mauro Carvalho Chehab <mchehab@...hat.com>,
Tony Luck <tony.luck@...el.com>,
Taku Izumi <izumi.taku@...fujitsu.com>,
Toshi Kani <toshi.kani@...com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-pci@...r.kernel.org, Russell King <linux@....linux.org.uk>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 00/22] PCI: Iterate pci host bridge instead of pci root bus
On Wednesday, February 06, 2013 01:53:50 PM Yinghai Lu wrote:
> On Wed, Feb 6, 2013 at 1:43 PM, Rafael J. Wysocki <rjw@...k.pl> wrote:
> > On Wednesday, February 06, 2013 01:28:27 PM Yinghai Lu wrote:
> >> so you still did not answer you want 1 or 2 yet:
> >>
> >> for sgi_hotplug,
> >>
> >> 1. still keep the module support, and register acpi_pci_driver later.
> >> 2. built-in support only, and need to register acpi_pci_driver early.
> >
> > Please work with the assumption that acpi_pci_driver is not going to be there
> > any more.
> >
>
> I think I could change ioapic and iommu hotplug to weak add/remove because they
> should be built-in by nature.
>
> but how about others like sgi_hotplug etc?
I'd really prefer to wait for the patchset removing acpi_pci_driver (from
Myron) before proceeding with more changes in that area.
Myron, do you have a prototype based on the current linux-next?
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists