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: <4EF26D63.10006@zytor.com>
Date:	Wed, 21 Dec 2011 15:36:03 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Greg KH <greg@...ah.com>
CC:	Kay Sievers <kay.sievers@...y.org>,
	Thomas Renninger <trenn@...e.de>,
	Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
	Andi Kleen <ak@...ux.intel.com>, axboe@...nel.dk,
	herbert@...dor.hengli.com.au, ying.huang@...el.com, lenb@...nel.org
Subject: Re: [PATCH 9/8] CPU: Introduce ARCH_HAS_CPU_AUTOPROBE and X86 parts

On 12/21/2011 03:29 PM, Greg KH wrote:
> On Wed, Dec 21, 2011 at 04:32:28PM +0100, Kay Sievers wrote:
>> 2011/12/21 Thomas Renninger<trenn@...e.de>:
>>
>> Cool. That sounds good. Nice work. Thanks.
>>
>> Adding Greg, so he's in the loop.
>>
>> Greg, Andi's upcoming CPU modaliases are temporarily hooked into the
>> 'cpuid' class devices to make them work with userspace, which isn't
>> possible with the weird sysdev stuff.
>>
>> We don't want to depend on the 'cpuid' class, but hook into the real
>> 'cpu' subsystem. This switches them over after we have the
>> sysdev-cpu-conversion stuff merged.
>
> Ok, but what does this mean now for my tree as I've taken your patches?
>

If I understand Kay right it means that once this tree and the patches 
from Kay are both upstream we can apply the cleanup patch.

Kay, is that correct?

	-hpa

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