RE: [PATCH v3 1/6] hv: Modify vmbus to search for all MMIO ranges available

[Jake Oshins]

> -----Original Message-----
> From: Vitaly Kuznetsov [mailto:vkuznets@xxxxxxxxxx]
> Sent: Wednesday, June 17, 2015 10:28 AM
> To: Jake Oshins
> Cc: gregkh@xxxxxxxxxxxxxxxxxxx; KY Srinivasan; linux-
> kernel@xxxxxxxxxxxxxxx; devel@xxxxxxxxxxxxxxxxxxxxxx; olaf@xxxxxxxxx;
> apw@xxxxxxxxxxxxx; 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?

-- Jake Oshins

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/