lkml.org 
[lkml]   [2015]   [Jun]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
Date
From
SubjectRe: [PATCH v3 1/6] hv: Modify vmbus to search for all MMIO ranges available
On Wed, Jun 17, 2015 at 05:41:58PM +0000, Jake Oshins wrote:
> > -----Original Message-----
> > From: Vitaly Kuznetsov [mailto:vkuznets@redhat.com]
> > Sent: Wednesday, June 17, 2015 10:28 AM
> > To: Jake Oshins
> > Cc: gregkh@linuxfoundation.org; KY Srinivasan; linux-
> > kernel@vger.kernel.org; devel@linuxdriverproject.org; olaf@aepfle.de;
> > apw@canonical.com; Haiyang Zhang; Mike Ebersol
> > Subject: Re: [PATCH v3 1/6] hv: Modify vmbus to search for all MMIO ranges
> > available
> > > }
> > >
> > > @@ -1047,6 +1121,7 @@ static struct acpi_driver vmbus_acpi_driver = {
> > > .ids = vmbus_acpi_device_ids,
> > > .ops = {
> > > .add = vmbus_acpi_add,
> > > + .remove = vmbus_acpi_remove,
> >
> > This will probably need rebasing on top of current char-misc-next tree
> > as we already have commit e4ecb41c: "Drivers: hv: vmbus: introduce
> > vmbus_acpi_remove" there.
> >
>
> Thanks. Please educate me since I'm new around here. What should I
> do in response to this message? Wait for this tree to be pulled into
> the mainline and resend after rebasing? Something more proactive?

It's KY's job to do this type of thing, he should handle this for you :)

greg k-h


\
 
 \ /
  Last update: 2015-06-17 21:41    [W:0.424 / U:0.112 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site