linux-kernel - [PATCH 0/5] ACPI: Rework acpi_bus

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:	Mon, 14 Jan 2013 22:33:57 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	ACPI Devel Maling List <linux-acpi@...r.kernel.org>
Cc:	Bjorn Helgaas <bhelgaas@...gle.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Toshi Kani <toshi.kani@...com>,
	Yinghai Lu <yinghai@...nel.org>,
	Jiang Liu <jiang.liu@...wei.com>,
	Taku Izumi <izumi.taku@...fujitsu.com>
Subject: [PATCH 0/5] ACPI: Rework acpi_bus_trim()

Hi All,

This series of patches changes the way acpi_bus_trim() works so that,
eventually, it walks the namespace twice detaching (ACPI) drivers from
device nodes being removed in the first pass and removing the device
nodes in the second pass.

The first two patches are just cleanups removing unused stuff:

[1/5] Remove the ops field from struct acpi_device (unrelated to the rest).
[2/5] Drop the second argument of acpi_device_unregister().

The next three patches actually rework acpi_bus_trim() in three steps:

[3/5] Drop the second argument of acpi_bus_trim() (all callers pass 1 in there
      anyway.
[4/5] Reimplement acpi_bus_trim() using acpi_walk_namespace().
[3/5] Make acpi_bus_trim() carry out two passes as described above.

I'm aware of the fact that this will conflict with the patches that Yinghai
posted a few days ago, but in my opinion the changes here are prerequisite for
the Yinghai's patchset.

Thanks,
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/