All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Gene Heskett <gheskett@wdtv.com>
Cc: Borislav Petkov <bp@alien8.de>,
	Boris Ostrovsky <boris.ostrovsky@amd.com>,
	Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
	mingo@elte.hu, tglx@linutronix.de,
	herrmann.der.user@googlemail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86, microcode, AMD: Add support for family 16h processors
Date: Sat, 17 Nov 2012 11:41:04 -0800	[thread overview]
Message-ID: <50A7E850.6070708@zytor.com> (raw)
In-Reply-To: <201211171334.34239.gheskett@wdtv.com>

On 11/17/2012 10:34 AM, Gene Heskett wrote:>
> And I don't see anything there that looks like a 'patch level'.
> The ucode obviously can, which is what counts in this game of horseshoes.  
> Perhaps something in that very long 'flags' string?
> 

What kernel version is this?

	-hpa



  reply	other threads:[~2012-11-17 19:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-15 18:41 [PATCH] x86, microcode, AMD: Add support for family 16h processors Boris Ostrovsky
2012-11-15 20:24 ` Andreas Herrmann
2012-11-15 20:45 ` Henrique de Moraes Holschuh
2012-11-15 21:26   ` Boris Ostrovsky
2012-11-15 21:48     ` H. Peter Anvin
2012-11-15 21:49     ` Henrique de Moraes Holschuh
2012-11-15 21:55     ` Andreas Herrmann
2012-11-15 23:01   ` Gene Heskett
2012-11-15 23:35     ` Boris Ostrovsky
2012-11-17 14:41       ` Borislav Petkov
2012-11-17 15:29         ` Henrique de Moraes Holschuh
2012-11-17 15:31           ` Borislav Petkov
2012-11-17 18:34         ` Gene Heskett
2012-11-17 19:41           ` H. Peter Anvin [this message]
2012-11-17 20:07             ` Gene Heskett
2012-11-17 20:42               ` H. Peter Anvin
2012-11-17 19:54     ` Andreas Herrmann
2012-11-17 20:11       ` Gene Heskett
2012-11-19 14:23         ` Borislav Petkov
2012-11-15 21:55 ` [tip:x86/urgent] " tip-bot for Boris Ostrovsky
2012-11-21  7:36 ` tip-bot for Boris Ostrovsky

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=50A7E850.6070708@zytor.com \
    --to=hpa@zytor.com \
    --cc=boris.ostrovsky@amd.com \
    --cc=bp@alien8.de \
    --cc=gheskett@wdtv.com \
    --cc=herrmann.der.user@googlemail.com \
    --cc=hmh@hmh.eng.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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.