On Thu, 12 Jan 2017 02:32:24 +0000
KY Srinivasan <[email protected]> wrote:

> > -----Original Message-----
> > From: Greg KH [mailto:[email protected]]
> > Sent: Tuesday, January 10, 2017 9:27 AM
> > To: KY Srinivasan <[email protected]>
> > Cc: [email protected]; [email protected];
> > [email protected]; [email protected]; [email protected];
> > [email protected]; [email protected];
> > [email protected]; [email protected]; [email protected]; [email protected]
> > Subject: Re: [PATCH 01/18] Drivers: hv: vmbus: Move the definition of
> > hv_x64_msr_hypercall_contents
> > 
> > On Fri, Dec 30, 2016 at 01:35:55PM -0800, [email protected]
> > wrote:  
> > > From: K. Y. Srinivasan <[email protected]>
> > >
> > > As part of the effort to separate out architecture specific code, move the
> > > definition of hv_x64_msr_hypercall_contents to x86 specific header file.
> > >
> > > Signed-off-by: K. Y. Srinivasan <[email protected]>
> > > ---
> > >  arch/x86/include/asm/mshyperv.h |   12 ++++++++++++
> > >  drivers/hv/hyperv_vmbus.h       |   15 ---------------
> > >  2 files changed, 12 insertions(+), 15 deletions(-)  
> > 
> > This series doesn't apply against my tree.  Can you please refresh it
> > and resend?  
> 
> Will do.
> 
> K. Y

Send me the patches, I have a vmbus-next tree ready for pull request.
_______________________________________________
devel mailing list
[email protected]
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

Reply via email to