public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Borislav Petkov <bp@amd64.org>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Jacob Shin <jacob.shin@amd.com>,
	Andre Przywara <andre.przywara@amd.com>,
	jeremy@goop.org, xen-devel@lists.xensource.com,
	LKML <linux-kernel@vger.kernel.org>,
	Jan Beulich <JBeulich@suse.com>, Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 0/4] x86, CPU, AMD: Cleanup AMD-specific MSR-rw users
Date: Fri, 01 Jun 2012 08:06:55 -0700	[thread overview]
Message-ID: <4FC8DA8F.4070602@zytor.com> (raw)
In-Reply-To: <20120601145732.GA28216@aftab.osrc.amd.com>

On 06/01/2012 07:57 AM, Borislav Petkov wrote:
> On Fri, Jun 01, 2012 at 07:53:26AM -0700, H. Peter Anvin wrote:
>> Looks good.  This can be for 3.6, right (no immediate urgency)?
> 
> None on arch/x86/ - simply correctness fixes.
> 
> And I'm assuming since you took Konrad's patch, there are no pending
> issues for xen either.
> 
> So yeah, this can wait for 3.6, IMHO.
> 

Great!  Will queue up shortly.

	-hpa


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


  reply	other threads:[~2012-06-01 15:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1338562358-28182-1-git-send-email-bp@amd64.org>
2012-06-01 14:53 ` [PATCH 0/4] x86, CPU, AMD: Cleanup AMD-specific MSR-rw users H. Peter Anvin
2012-06-01 14:57   ` Borislav Petkov
2012-06-01 15:06     ` H. Peter Anvin [this message]
     [not found] ` <1338562358-28182-2-git-send-email-bp@amd64.org>
2012-06-06 20:06   ` [PATCH 1/4] x86, pvops: Remove hooks for {rd,wr}msr_safe_regs Konrad Rzeszutek Wilk
2012-06-07 21:58   ` [tip:x86/cpu] " tip-bot for Andre Przywara
     [not found] ` <1338562358-28182-4-git-send-email-bp@amd64.org>
2012-06-06 20:07   ` [PATCH 3/4] x86, AMD: Fix crash as Xen Dom0 on AMD Trinity systems Konrad Rzeszutek Wilk
2012-06-06 22:00   ` H. Peter Anvin
2012-06-07  7:21     ` Borislav Petkov
2012-06-07  7:49       ` Andre Przywara
2012-06-07  8:08         ` Greg KH
2012-06-07  8:18           ` Andre Przywara
2012-06-07 13:25             ` [GIT PULL] x86, CPU, AMD: Cleanup AMD-specific MSR-rw users Borislav Petkov
2012-06-07 16:27           ` [PATCH 3/4] x86, AMD: Fix crash as Xen Dom0 on AMD Trinity systems H. Peter Anvin
2012-06-07 22:00   ` [tip:x86/cpu] x86, cpu, amd: " tip-bot for Andre Przywara
     [not found] ` <1338562358-28182-3-git-send-email-bp@amd64.org>
2012-06-01 18:22   ` [PATCH 2/4] x86, CPU: Fix show_msr MSR accessing function Yinghai Lu
2012-06-01 22:50     ` Borislav Petkov
2012-06-06 20:07   ` Konrad Rzeszutek Wilk
2012-06-07 21:59   ` [tip:x86/cpu] x86, cpu: " tip-bot for Borislav Petkov
     [not found] ` <1338562358-28182-5-git-send-email-bp@amd64.org>
2012-06-06 20:07   ` [PATCH 4/4] x86, CPU, AMD: Deprecate AMD-specific MSR variants Konrad Rzeszutek Wilk
2012-06-07 22:01   ` [tip:x86/cpu] x86, cpu, amd: " tip-bot for Borislav Petkov

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=4FC8DA8F.4070602@zytor.com \
    --to=hpa@zytor.com \
    --cc=JBeulich@suse.com \
    --cc=andre.przywara@amd.com \
    --cc=bp@amd64.org \
    --cc=jacob.shin@amd.com \
    --cc=jeremy@goop.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=xen-devel@lists.xensource.com \
    /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