public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Borislav Petkov <bp@amd64.org>
Cc: Andreas Herrmann <andreas.herrmann3@amd.com>,
	x86 <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] x86, microcode, AMD: Fixes for next merge window
Date: Thu, 15 Dec 2011 08:13:07 +0100	[thread overview]
Message-ID: <20111215071307.GE14237@elte.hu> (raw)
In-Reply-To: <20111214145846.GD23589@aftab>


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

> Hi Ingo,
> 
> as promised, please pull from the branch below to receive the following
> fixes, they could be queued for the next merge window and simmer a while
> in linux-next until then.
> 
> Thanks.
> 
> The following changes since commit dc47ce90c3a822cd7c9e9339fe4d5f61dcb26b50:
> 
>   Linux 3.2-rc5 (2011-12-09 15:09:32 -0800)
> 
> are available in the git repository at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git ucode-verify-size
> 
> Borislav Petkov (5):
>       x86, microcode, AMD: Add a vendor-specific exit function
>       x86, microcode, AMD: Add a reusable buffer
>       x86, microcode, AMD: Simplify ucode verification
>       x86, microcode, AMD: Exit early on success
>       x86, microcode, AMD: Update copyrights
> 
>  arch/x86/include/asm/microcode.h |    2 +
>  arch/x86/kernel/microcode_amd.c  |  209 +++++++++++++++++++++-----------------
>  arch/x86/kernel/microcode_core.c |    5 +
>  3 files changed, 121 insertions(+), 95 deletions(-)

Pulled, thanks a lot Boris!

	Ingo

      reply	other threads:[~2011-12-15  7:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-14 14:58 [GIT PULL] x86, microcode, AMD: Fixes for next merge window Borislav Petkov
2011-12-15  7:13 ` 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=20111215071307.GE14237@elte.hu \
    --to=mingo@elte.hu \
    --cc=andreas.herrmann3@amd.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox