From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <borislav.petkov@amd.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andreas Herrmann <andreas.herrmann3@amd.com>,
Kay Sievers <kay.sievers@vrfy.org>, Dave Jones <davej@redhat.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [GIT PULL] x86 microcode fix for 3.4
Date: Sat, 14 Apr 2012 13:32:35 +0200 [thread overview]
Message-ID: <20120414113235.GD24688@gmail.com> (raw)
In-Reply-To: <20120413101021.GC27686@aftab>
* Borislav Petkov <borislav.petkov@amd.com> wrote:
> Hi Ingo,
>
> please pull the following fix for 3.4 from Andreas. This is seen by
> people using 3.3 too thus the stable tagging.
>
> Thanks.
>
> ---
> The following changes since commit 0034102808e0dbbf3a2394b82b1bb40b5778de9e:
>
> Linux 3.4-rc2 (2012-04-07 18:30:41 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git tags/microcode-fix-for-3.4
>
> for you to fetch changes up to 283c1f2558ef4a4411fe908364b15b73b6ab44cf:
>
> x86, microcode: Ensure that module is only loaded on supported AMD CPUs (2012-04-13 11:51:05 +0200)
>
> ----------------------------------------------------------------
> A two-patch fix from Andreas taking care of a sysfs warning when the
> microcode driver is loaded on unsupported platforms.
>
> ----------------------------------------------------------------
> Andreas Herrmann (2):
> x86, microcode: Fix sysfs warning during module unload on unsupported CPUs
> x86, microcode: Ensure that module is only loaded on supported AMD CPUs
>
> arch/x86/kernel/microcode_amd.c | 12 +++++++-----
> arch/x86/kernel/microcode_core.c | 10 ++++------
> 2 files changed, 11 insertions(+), 11 deletions(-)
Pulled, thanks!
Ingo
prev parent reply other threads:[~2012-04-14 11:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 10:10 [GIT PULL] x86 microcode fix for 3.4 Borislav Petkov
2012-04-14 11:32 ` 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=20120414113235.GD24688@gmail.com \
--to=mingo@kernel.org \
--cc=andreas.herrmann3@amd.com \
--cc=borislav.petkov@amd.com \
--cc=davej@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.