public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: KY Srinivasan <kys@microsoft.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
	"olaf@aepfle.de" <olaf@aepfle.de>,
	"apw@canonical.com" <apw@canonical.com>,
	"jasowang@redhat.com" <jasowang@redhat.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"JBeulich@suse.com" <JBeulich@suse.com>,
	"bp@alien8.de" <bp@alien8.de>
Subject: Re: [PATCH 1/1] Drivers: hv: vmbus: Use the new infrastructure for delivering VMBUS interrupts
Date: Wed, 13 Feb 2013 10:52:39 -0800	[thread overview]
Message-ID: <20130213185239.GB16645@kroah.com> (raw)
In-Reply-To: <511BDD2A.8020002@zytor.com>

On Wed, Feb 13, 2013 at 10:36:26AM -0800, H. Peter Anvin wrote:
> On 02/13/2013 10:23 AM, Greg KH wrote:
> > On Wed, Feb 13, 2013 at 10:19:15AM -0800, H. Peter Anvin wrote:
> >> Sounds like we have the joy of a cross-tree dependency...
> > 
> > Yeah, a mess.
> > 
> > KY, how about I just wait until all of this gets merged with Linus for
> > 3.9-rc1, and then you resend me the patches you have to take advantage
> > of these new bits?  That makes it easy for everyone involved.
> > 
> 
> The other option is you can pull tip:x86/hyperv from me... it has *only*
> these changes.  I can then let you push them to Linus or I can push them
> to Linus before you push your tree.

Nah, I'll just wait, it's not that big of a deal here, it will all make
it into 3.9-final eventually.

greg k-h

  reply	other threads:[~2013-02-13 18:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06 15:25 [PATCH 1/1] Drivers: hv: vmbus: Use the new infrastructure for delivering VMBUS interrupts K. Y. Srinivasan
2013-02-06 19:13 ` Greg KH
2013-02-09 14:09   ` KY Srinivasan
2013-02-13  0:30   ` H. Peter Anvin
2013-02-13  0:43     ` KY Srinivasan
2013-02-13  0:46       ` H. Peter Anvin
2013-02-13  0:50         ` KY Srinivasan
2013-02-13  0:59           ` H. Peter Anvin
2013-02-13 14:07     ` KY Srinivasan
2013-02-13 16:22       ` Greg KH
2013-02-13 17:08         ` KY Srinivasan
2013-02-13 18:19           ` H. Peter Anvin
2013-02-13 18:23             ` Greg KH
2013-02-13 18:33               ` KY Srinivasan
2013-02-13 18:36               ` H. Peter Anvin
2013-02-13 18:52                 ` Greg KH [this message]
2013-02-17 18:13                   ` KY Srinivasan
2013-02-17 18:25                     ` Greg KH
2013-02-17 18:51                       ` KY Srinivasan
2013-02-17 19:15                         ` H. Peter Anvin
  -- strict thread matches above, loose matches on Subject: below --
2013-02-17 19:30 K. Y. Srinivasan
2013-02-27 14:39 ` 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=20130213185239.GB16645@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=JBeulich@suse.com \
    --cc=apw@canonical.com \
    --cc=bp@alien8.de \
    --cc=devel@linuxdriverproject.org \
    --cc=hpa@zytor.com \
    --cc=jasowang@redhat.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf@aepfle.de \
    --cc=tglx@linutronix.de \
    --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