From: Borislav Petkov <bp@amd64.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: X86-ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Borislav Petkov <borislav.petkov@amd.com>
Subject: [PATCH 0/2] x86, microcode: AMD adjustments
Date: Mon, 17 Oct 2011 17:25:13 +0200 [thread overview]
Message-ID: <1318865115-9904-1-git-send-email-bp@amd64.org> (raw)
From: Borislav Petkov <borislav.petkov@amd.com>
Hi,
this should take care of the recent addition of microcode revision to
/proc/cpuinfo for AMD too. Patches are against tip/x88/microcode and
available also on
git://amd64.org/linux/bp.git tip-ucode
Please pull,
thanks.
The following changes since commit ca8bc8dc044793ee4d59ff7fe40138eee27d0325:
coretemp: Get microcode revision from cpu_data (2011-10-14 13:16:42 +0200)
are available in the git repository at:
git://amd64.org/linux/bp.git tip-ucode
Borislav Petkov (2):
x86, microcode: Correct microcode revision format
x86, microcode, AMD: Add microcode revision to /proc/cpuinfo
arch/x86/kernel/cpu/amd.c | 4 ++++
arch/x86/kernel/cpu/mcheck/mce.c | 2 +-
arch/x86/kernel/cpu/proc.c | 2 +-
arch/x86/kernel/microcode_amd.c | 5 +++--
4 files changed, 9 insertions(+), 4 deletions(-)
next reply other threads:[~2011-10-17 15:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 15:25 Borislav Petkov [this message]
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
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=1318865115-9904-1-git-send-email-bp@amd64.org \
--to=bp@amd64.org \
--cc=borislav.petkov@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).