ACPI: use handle, not device, in system notification path
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | ACPI: simplify notification debug messagesdrivers/ | +3 | 0 replies | |
| 2/4 | ACPI: remove unused "status_changed" return value from Check Device handlingdrivers/ | +3 | 0 replies | |
| 3/4 | ACPI: remove unused return values from Bus Check & Device Check handlingdrivers/ | +11 | 0 replies | |
| 4/4 | ACPI: use handle, not device, in system notification pathdrivers/ | +15 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/4] ACPI: use handle, not device, in system notification path
Currently, ACPI hotplug is mostly handled in drivers. I'm working on moving that hotplug support out of drivers and into the Linux/ACPI core.
These patches change the Linux/ACPI notify handling to use the acpi_handle a bit longer before looking up an acpi_device.
System notifications often deal with device presence and status change. In these cases, we may not have an acpi_device. For example, we may get a Device Check notification on an object that previously was not present. Since the object was not present, we would not have had an acpi_device for it.
Note: The last patch in this series depends on this previous patch that is not upstream yet:
http://patchwork.kernel.org/patch/21076/
Comments welcome.
---
Bjorn Helgaas (4):
ACPI: use handle, not device, in system notification path
ACPI: remove unused return values from Bus Check & Device Check handling
ACPI: remove unused "status_changed" return value from Check Device handling
ACPI: simplify notification debug messages
drivers/acpi/bus.c | 93 +++++++++++++--------------------------------------- 1 files changed, 23 insertions(+), 70 deletions(-)
Signature · 1 line
Bjorn