linux-kernel - Re: [PATCH 2/2] x86, microcode, AMD: Add microcode revision to /proc/cpuinfo

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: <20111023114821.GE5156@elte.hu>
Date:	Sun, 23 Oct 2011 13:48:21 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Borislav Petkov <bp@...64.org>
Cc:	X86-ML <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] x86, microcode, AMD: Add microcode revision to
 /proc/cpuinfo


* Borislav Petkov <bp@...64.org> wrote:

> On Tue, Oct 18, 2011 at 02:25:10AM -0400, Ingo Molnar wrote:
> > The standard way we mention commits in changelogs is:
> > 
> >   Enable microcode revision output for AMD after commit 506ed6b53e00 
> >   ("x86, intel: Output microcode revision in /proc/cpuinfo") did it 
> >   for Intel.
> > 
> > ... because humans are pretty bad at transforming sha1's to the real 
> > commit title when reading such text.
> 
> Why, I thought transforming sha1's to commit messages is one of the job
> requirements of serious kernel hackers.
> 
> :-)

But they are not the only ones reading changelogs ;-)

> > Please fix the changelog for the first commit as well.
> 
> Done, git branch at
> 
> git://amd64.org/linux/bp.git tip-ucode
> 
> updated.

Pulled, thanks,

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