mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Borislav Petkov <bp@amd64.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Jan Beulich <JBeulich@suse.com>
Subject: Re: [GIT PULL] x86, microcode fixes for 3.2
Date: Mon, 5 Dec 2011 10:26:12 +0100	[thread overview]
Message-ID: <20111205092612.GB29641@elte.hu> (raw)
In-Reply-To: <20111202194658.GF15204@aftab>


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

> On Mon, Nov 28, 2011 at 09:43:11PM +0100, Borislav Petkov wrote:
> > Hi Ingo,
> > 
> > please pull the following two fixes for the microcode machinery.
> > 
> > Thanks.
> > 
> > The following changes since commit caca6a03d365883564885f2c1da3e88dcf65d139:
> > 
> >   Linux 3.2-rc3 (2011-11-23 20:20:28 -0800)
> > 
> > are available in the git repository at:
> >   git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git ucode
> > 
> > Borislav Petkov (1):
> >       x86, microcode, AMD: Restrict microcode reporting
> > 
> > Srivatsa S. Bhat (1):
> >       x86, microcode: Fix the failure path of microcode update driver init code
> 
> Since you haven't pulled yet, I've updated this one with the better
> version below, branch above has been updated too:
> 
> --
> From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
> Date: Mon, 7 Nov 2011 18:05:32 +0530
> Subject: [PATCH] x86, microcode: Fix the failure path of microcode update
>  driver init code
> 
> The microcode update driver's initialization code does not handle
> failures correctly. This patch fixes this issue.
> 
> Signed-off-by: Jan Beulich <JBeulich@suse.com>
> Signed-off-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
> Link: http://lkml.kernel.org/r/20111107123530.12164.31227.stgit@srivatsabhat.in.ibm.com
> Link: http://lkml.kernel.org/r/4ED8E2270200007800065120@nat28.tlf.novell.com
> Signed-off-by: Borislav Petkov <borislav.petkov@amd.com>
> ---

Mind respinning this once more against latest -git? There's a 
new conflict due to:

  8e8da023f5af: x86: Fix boot failures on older AMD CPU's

Thanks,

	Ingo

  reply	other threads:[~2011-12-05  9:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-28 20:43 Borislav Petkov
2011-12-02 19:46 ` Borislav Petkov
2011-12-05  9:26   ` Ingo Molnar [this message]
2011-12-05 15:10     ` Borislav Petkov
2012-03-25 19:27       ` H. Peter Anvin
2012-03-26  8:48         ` Borislav Petkov
2012-03-26 14:52           ` H. Peter Anvin
2012-03-26 15:25             ` Borislav Petkov
2012-03-26 17:56               ` H. Peter Anvin

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=20111205092612.GB29641@elte.hu \
    --to=mingo@elte.hu \
    --cc=JBeulich@suse.com \
    --cc=bp@amd64.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srivatsa.bhat@linux.vnet.ibm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®