linux-kernel - Re: [PATCH 0/4] Decouple X86_32 dependency from the ISA Kconfig option

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:	Wed, 13 Apr 2016 10:48:42 -0400
From:	William Breathitt Gray <vilhelm.gray@...il.com>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
	gregkh@...uxfoundation.org, x86@...nel.org,
	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
	alsa-devel@...a-project.org
Subject: Re: [PATCH 0/4] Decouple X86_32 dependency from the ISA Kconfig
 option

On Wed, Apr 13, 2016 at 04:38:38PM +0200, Ingo Molnar wrote:
>Ah, ok, so it's for enabling real hardware, not just a cleanup, right? You might 
>want to put that info into the boilerplate mail or so.
>
>I'm perfectly fine with all the patches that touch x86 code:
>
>  Acked-by: Ingo Molnar <mingo@...nel.org>
>
>I suppose you'd like to have these in the driver tree, all in one place?
>
>Thanks,
>
>	Ingo

Ah yes, in retrospect I should have made it clear that this was for
supporting hardware rather than simply code cleanup. That was an
oversight on my part not to have made it more explicit.

Introducing everything to the driver tree would be most convenient, thus
allowing me to quickly release my subsequent patches which will be
rebased on top of these.

William Breathitt Gray