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] [day] [month] [year] [list]
Message-ID: <505BCC1C.6000006@acm.org>
Date:	Thu, 20 Sep 2012 21:08:28 -0500
From:	Corey Minyard <tcminyard@...il.com>
To:	Matthew Garrett <mjg59@...f.ucam.org>
CC:	Corey Minyard <cminyard@...sta.com>, yakui.zhao@...el.com,
	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] ACPI: Reorder IPMI driver before any other ACPI drivers

On 09/20/2012 08:26 PM, Matthew Garrett wrote:
> On Thu, Sep 20, 2012 at 08:19:48PM -0500, Corey Minyard wrote:
>> On 09/20/2012 04:46 PM, Matthew Garrett wrote:
>>> Drivers may make calls that require the ACPI IPMI driver to have been
>>> initialised already, so make sure that it appears earlier in the build
>>> order.
>> The IPMI driver uses the ACPI namespace as an option to know the
>> address and characteristics of the device.  Does that still work?
> Yes, the ACPI interpreter is initialised earlier than the IPMI driver
> discovery.
>
Cool, I'm good with these, then.

Thanks,

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ