linux-kernel - [PATCH 0/3] ACPI / dock: Rework the handling of dock notifications

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 11 Feb 2014 01:09:32 +0100
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	ACPI Devel Maling List <linux-acpi@...r.kernel.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>
Subject: [PATCH 0/3] ACPI / dock: Rework the handling of dock notifications

Hi All,

This is on top of the current linux-next branch of linux-pm.git.

The handling of ACPI dock notifications doesn't require a notify handler to
be installed for every dock device object.  Moreover, the namespace doesn't
have to be scanned upfront to discover those objects and the ACPI container
code should be made avoid trying to handle dock notifications (in case dock
stations have container device IDs).

The series makes the changes following from the above observations and a
couple of improvements on top of them.

[1/3] Dispatch ACPI dock notifications from the global notify handler.
[2/3] Pass ACPI device pointer to acpi_device_is_battery() (which is a new
      helper function added by [1/3]).
[3/3] Associate dock platform devices with ACPI device objects

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/