[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <3011875.q18rCmXyYX@vostro.rjw.lan>
Date: Wed, 19 Feb 2014 02:26:10 +0100
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: ACPI Devel Maling List <linux-acpi@...r.kernel.org>
Cc: Linux PCI <linux-pci@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Bjorn Helgaas <bhelgaas@...gle.com>, Tejun Heo <tj@...nel.org>,
Aaron Lu <aaron.lu@...el.com>
Subject: [PATCH 0/9] ACPI / dock / PCI / SATA: Simplify ACPI dock handling
Hi All,
This series is on top of the current linux-next and it removes one of the
ugliest, in my opinion, things related to ACPI dock support, which is the
registration and unregistration of dock operations that makes it necessary
to register dock devices *twice* with the dock driver.
[1/9] After recent changes ACPIPHP doesn't need to clear the event
callback (introduced in linux-next) for dock stations.
[2/9] Add .fixup() callback to struct acpi_hotplug_context for PCI devices
located in dock stations.
[3/9] Store ACPI device object pointers instead of ACPI handles in the internal
data structures used by the dock driver.
[4/9] Make the dock driver use callback pointers from the hotplug contexts of
ACPI device objects and modify ACPIPHP to use that mechanism (instead of
registering a special set of dock operations for each device).
[5/9] Add .uevent() callback to struct acpi_hotplug_context for SATA devices
located in dock stations.
[6/9] Make SATA ACPI support code use hotplug contexts of ACPI device objects
(instead of dock operations).
[7/9] Drop struct acpi_dock_ops and all code related to it (no more users).
[8/9] Drop remove_dock_dependent_devices() (this is a cleanup that doesn't
really depend on the rest of the series).
[9/9] Update the copyright notice in dock.c.
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