linux-kernel - Re: [tip:x86/microcode] x86, microcode: Move to a proper location

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:	Tue, 14 Jan 2014 20:27:02 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	linux-kernel@...r.kernel.org, mingo@...nel.org,
	Aravind.Gopalakrishnan@....com, tglx@...utronix.de, bp@...e.de,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/microcode] x86, microcode: Move to a proper location

On Tue, Jan 14, 2014 at 11:18:57AM -0800, H. Peter Anvin wrote:
> arch/x86/cpu/microcode seems clean. I'm wondering if what is mostly
> currently in arch/x86/kernel/cpu should be mostly in something like
> arch/x86/cpu/init.

Yeah, I can start reorganizing stuff slowly and with time, the best
place will dawn on us. One thing's for sure, the "kernel" in the path is
kinda redundant because, as Ingo said, it is all kernel.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
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/