linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Borislav Petkov <bp@amd64.org>
Cc: Ingo Molnar <mingo@kernel.org>,
	Andreas Herrmann <andreas.herrmann3@amd.com>,
	Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
	x86 <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] x86, microcode, AMD: Per-family patches cache
Date: Mon, 20 Aug 2012 16:23:09 -0700	[thread overview]
Message-ID: <5032C6DD.7060506@zytor.com> (raw)
In-Reply-To: <20120817143035.GA25700@aftab.osrc.amd.com>

On 08/17/2012 07:30 AM, Borislav Petkov wrote:
> Hi guys,
>
> please pull, thanks.
>
> The following changes since commit d9875690d9b89a866022ff49e3fcea892345ad92:
>
>    Linux 3.6-rc2 (2012-08-16 14:51:24 -0700)
>
> are available in the git repository at:
>
>    git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git tags/microcode-updates-for-3.7
>
> for you to fetch changes up to cd692919bed1d59a440ffaed585ebc3c9d8c3406:
>
>    x86, microcode, AMD: Rewrite patch application procedure (2012-08-17 14:17:42 +0200)
>

Hmmm... this isn't actually present on git.kernel.org, and 01/12 is 
missing from your "v0" patchset on LKML (nevermind that a "v0" 
designator screams "don't apply"...)

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2012-08-20 23:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-17 14:30 [GIT PULL] x86, microcode, AMD: Per-family patches cache Borislav Petkov
2012-08-20 23:23 ` H. Peter Anvin [this message]
2012-08-21  9:16   ` Borislav Petkov
2012-08-22 22:48     ` H. Peter Anvin
2012-08-22 23:26       ` H. Peter Anvin
2012-08-23  9:51         ` Borislav Petkov
2012-08-22 21:52   ` 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=5032C6DD.7060506@zytor.com \
    --to=hpa@zytor.com \
    --cc=andreas.herrmann3@amd.com \
    --cc=bp@amd64.org \
    --cc=hmh@hmh.eng.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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;
as well as URLs for NNTP newsgroup(s).