[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1693151.2qrLZHyp0o@vostro.rjw.lan>
Date: Wed, 29 Jan 2014 00:57:06 +0100
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: ACPI Devel Maling List <linux-acpi@...r.kernel.org>
Cc: Bjorn Helgaas <bhelgaas@...gle.com>, Aaron Lu <aaron.lu@...el.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux PCI <linux-pci@...r.kernel.org>,
Mika Westerberg <mika.westerberg@...ux.intel.com>
Subject: Re: [PATCH 0/5][RFT] ACPI / hotplug / PCI: Consolidation of ACPIPHP with ACPI core device hotplug
On Tuesday, January 28, 2014 11:10:30 PM Rafael J. Wysocki wrote:
> Hi All,
>
> It looks like there's time for more adventurous stuff. :-)
>
> The following series is on top of the one I sent on Sunday:
>
> https://lkml.org/lkml/2014/1/26/191
>
> The final outcome of the patches below is that all ACPI hotplug notifications
> for PCI devices and for core system things like CPU, memory, PCI roots etc.,
> will be dispatched from acpi_bus_notify() and it is not necessary to install a
> separate hotplug notify handler for each device any more.
>
> [1/5] Attach ACPIPHP hotplug contexts to struct acpi_device objects.
> [2/5] Introduce wrappers for installing and removing hotplug notify handlers
> (those wrappers go away later on, but they are useful for separating
> changes).
> [3/5] Consolidate ACPI hotplug signaling for PCI and ACPI core.
> [4/5] Simplify notify handle registration wrapper.
> [5/5] Dispatch ACPI hotplug notifications for "core" devices and PCI from acpi_bus_notify().
Unfortunately, I realized that patches [3-5/5] were buggy. The bugs were
kind of subtle and might not be easy to reproduce, but they were bugs anyway. :-)
A respin of the whole series follows.
Thanks!
--
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