linux-kernel - Re: [PATCH -v2 0/2] x86, microcode: Reload ucode only per-system

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: <29cea64a-e041-48ba-bf3e-0965740b862b@email.android.com>
Date:	Mon, 02 Jul 2012 06:05:56 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Borislav Petkov <bp@...64.org>
CC:	Ingo Molnar <mingo@...nel.org>, X86-ML <x86@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Andreas Herrmann <andreas.herrmann3@....com>,
	Borislav Petkov <borislav.petkov@....com>
Subject: Re: [PATCH -v2 0/2] x86, microcode: Reload ucode only per-system

I put them into x86/microcode already.

Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote:

>On Sat, 2012-06-30 at 19:45 +0200, Borislav Petkov wrote:
>> Assuming there are no more objections to those, can we get them into,
>> say, tip:x86/microcode for a wider, linux-next testing?
>> 
>> Peter's stuff could go there too or through the perf tree - it's
>kinda
>> arbitrary though. 
>
>I've got them queued as such, Ingo's just hasn't gotten around to
>picking things up yet. Let me see if today is a good day for this.. :-)

-- 
Sent from my mobile phone. Please excuse brevity and lack of formatting.
--
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/