linux-kernel - Re: [PATCH 0/6] ACPI: Simplify namespace scanning for devices

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]

Message-ID: <50CDEFFE.7030509@gmail.com>
Date:	Sun, 16 Dec 2012 23:59:58 +0800
From:	Jiang Liu <liuj97@...il.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
CC:	ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Yinghai Lu <yinghai@...nel.org>,
	Toshi Kani <toshi.kani@...com>,
	Yijing Wang <wangyijing0307@...il.com>,
	Wen Congyang <wency@...fujitsu.com>
Subject: Re: [PATCH 0/6] ACPI: Simplify namespace scanning for devices

Hi Rafael,
	Great idea to get rid of the .start() staff, it could also
simplify our hotplug framework too.
	Thanks!
	Gerry

On 12/16/2012 09:47 PM, Rafael J. Wysocki wrote:
> Hi All,
> 
> This series is on top of the one I sent on Thursday:
> 
> https://lkml.org/lkml/2012/12/13/632
> 
> It goes one step farther and makes some simplifications that become possible
> after applying that patchset.
> 
> [1/6] Fold acpi_pci_root_start() into acpi_pci_root_add()
> [2/6] Remove acpi_start_single_object() and acpi_bus_start()
> [3/6] Remove the arguments of acpi_bus_add() that are not used
> [4/6] Drop the second argument of acpi_bus_scan()
> [5/6] Replace ACPI device add_type field with a match_driver flag
> [6/6] Make acpi_bus_scan() and acpi_bus_add() take only one argument
> 
> It survives booting on Toshiba Portege R500 without any visible issues.
> 
> Thanks,
> Rafael
> 
> 

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