From: Ingo Molnar <mingo@elte.hu>
To: Borislav Petkov <bp@amd64.org>
Cc: X86-ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] x86, microcode, AMD: Add microcode revision to /proc/cpuinfo
Date: Sun, 23 Oct 2011 13:48:21 +0200 [thread overview]
Message-ID: <20111023114821.GE5156@elte.hu> (raw)
In-Reply-To: <20111019142057.GA26786@aftab>
* Borislav Petkov <bp@amd64.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
prev parent reply other threads:[~2011-10-23 11:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 15:25 [PATCH 0/2] x86, microcode: AMD adjustments Borislav Petkov
2011-10-17 15:25 ` [PATCH 1/2] x86, microcode: Correct microcode revision format Borislav Petkov
2011-10-18 6:50 ` David Rientjes
2011-10-18 7:51 ` Borislav Petkov
2011-10-18 8:14 ` David Rientjes
2011-10-18 9:48 ` Borislav Petkov
2011-10-18 15:13 ` Andi Kleen
2011-10-18 15:49 ` Borislav Petkov
2011-10-17 15:25 ` [PATCH 2/2] x86, microcode, AMD: Add microcode revision to /proc/cpuinfo Borislav Petkov
2011-10-18 6:25 ` Ingo Molnar
2011-10-19 14:20 ` Borislav Petkov
2011-10-23 11:48 ` Ingo Molnar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111023114821.GE5156@elte.hu \
--to=mingo@elte.hu \
--cc=bp@amd64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.