[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <663c5ef1750e4aa3922c38e897c4903a@SN2PR03MB061.namprd03.prod.outlook.com>
Date: Sun, 17 Feb 2013 18:51:46 +0000
From: KY Srinivasan <kys@...rosoft.com>
To: Greg KH <gregkh@...uxfoundation.org>
CC: "H. Peter Anvin" <hpa@...or.com>,
"x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"olaf@...fle.de" <olaf@...fle.de>,
"apw@...onical.com" <apw@...onical.com>,
"jasowang@...hat.com" <jasowang@...hat.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"JBeulich@...e.com" <JBeulich@...e.com>,
"bp@...en8.de" <bp@...en8.de>
Subject: RE: [PATCH 1/1] Drivers: hv: vmbus: Use the new infrastructure for
delivering VMBUS interrupts
> -----Original Message-----
> From: Greg KH [mailto:gregkh@...uxfoundation.org]
> Sent: Sunday, February 17, 2013 1:25 PM
> To: KY Srinivasan
> Cc: H. Peter Anvin; x86@...nel.org; linux-kernel@...r.kernel.org;
> devel@...uxdriverproject.org; olaf@...fle.de; apw@...onical.com;
> jasowang@...hat.com; tglx@...utronix.de; JBeulich@...e.com; bp@...en8.de
> Subject: Re: [PATCH 1/1] Drivers: hv: vmbus: Use the new infrastructure for
> delivering VMBUS interrupts
>
> On Sun, Feb 17, 2013 at 06:13:49PM +0000, KY Srinivasan wrote:
> >
> >
> > > -----Original Message-----
> > > From: Greg KH [mailto:gregkh@...uxfoundation.org]
> > > Sent: Wednesday, February 13, 2013 1:53 PM
> > > To: H. Peter Anvin
> > > Cc: KY Srinivasan; x86@...nel.org; linux-kernel@...r.kernel.org;
> > > devel@...uxdriverproject.org; olaf@...fle.de; apw@...onical.com;
> > > jasowang@...hat.com; tglx@...utronix.de; JBeulich@...e.com;
> bp@...en8.de
> > > Subject: Re: [PATCH 1/1] Drivers: hv: vmbus: Use the new infrastructure for
> > > delivering VMBUS interrupts
> > >
> > > 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.
> >
> > Peter's check-ins are now in Linux-next. Should I send you the vmbus
> > patch that uses this infrastructure.
>
> No one can base their tree on linux-next, so no. Please wait for them
> to get into Linus's tree.
>
> Or send them to me now, with the instructions to apply them after
> 3.9-rc1, and I will save them for that point in time.
Thanks Greg. Will do.
K. Y
>
> thanks,
>
> greg k-h
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists