linux-kernel - Re: [PATCH 0/4] ACPI: Reorganize the core device management/enumeration code

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 30 Jul 2015 12:54:39 +0300
From:	Mika Westerberg <mika.westerberg@...ux.intel.com>
To:	"Rafael J. Wysocki" <rjw@...ysocki.net>
Cc:	ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/4] ACPI: Reorganize the core device
 management/enumeration code

On Tue, Jul 14, 2015 at 01:16:12AM +0200, Rafael J. Wysocki wrote:
> Hi,
> 
> The size and complexity of drivers/acpi/scan.c has bothered me for quite
> a while and since I'm working on a feature that will benefit from exposing
> some additional information under ACPI device objects in sysfs, I've decided
> to reorganize the code to move some things out of scan.c.
> 
> [1/4] Move all ACPI device code related to sysfs into a separate (new) file.
> [2/4] Move device matching code to bus.c.
> [3/4] Mode device notification, bus operations and driver management code to bus.c.
> [4/4] Register the ACPI bus type in acpi_bus_init().
> 
> No functional changes except for the [4/4] that will case ACPI to be disabled if
> the ACPI bus type cannot be registered.

Just noticed this series. If it is not too late, you can add my

Reviewed-by: Mika Westerberg <mika.westerberg@...ux.intel.com>

to the whole series.
--
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/