All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	Vadim Rozenfeld <vrozenfe@redhat.com>,
	Avi Kivity <avi@redhat.com>, Gleb Natapov <gleb@redhat.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	Hank Janssen <hjanssen@microsoft.com>
Subject: Re: [PATCH] x86: detect running on a HyperV system
Date: Thu, 6 May 2010 12:18:16 -0700	[thread overview]
Message-ID: <20100506191816.GA20874@kroah.com> (raw)
In-Reply-To: <4BE314CD.6060701@zytor.com>

On Thu, May 06, 2010 at 12:13:17PM -0700, H. Peter Anvin wrote:
> On 05/06/2010 12:08 PM, Greg KH wrote:
> > 
> > x86-maintainers, we need this patch in the tree to get a -staging driver
> > to work properly.  If you don't object, can I take it through the
> > staging tree?  Or do you want to take it in -tip?
> > 
> 
> I'd prefer to take it in -tip, partly because I would like to rework a
> few things -- including preexisting braindamage like c->x86_hyper_vendor
> (since when was hypervisor vendor a per-cpu property!?)

Heh, good point, but where should it live?

And I have no objection to taking it in -tip, thanks for doing so.

> I'll try to get to it today, if not feel free to bug me.

Will do :)

thanks again,

greg k-h

  reply	other threads:[~2010-05-06 19:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06 19:08 [PATCH] x86: detect running on a HyperV system Greg KH
2010-05-06 19:13 ` H. Peter Anvin
2010-05-06 19:18   ` Greg KH [this message]
2010-05-06 21:23     ` H. Peter Anvin
2010-05-07  1:49     ` H. Peter Anvin
2010-05-07 15:46       ` Greg KH
2010-05-07 16:20         ` Hank Janssen
2010-05-08  1:57 ` [tip:x86/cpu] x86: Detect running on a Microsoft " tip-bot for Ky Srinivasan

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=20100506191816.GA20874@kroah.com \
    --to=greg@kroah.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=haiyangz@microsoft.com \
    --cc=hjanssen@microsoft.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=vrozenfe@redhat.com \
    --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 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.