> -----Original Message----- > From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com] > Sent: Wednesday, June 17, 2015 10:28 AM > To: Jake Oshins > Cc: gre...@linuxfoundation.org; KY Srinivasan; linux- > ker...@vger.kernel.org; de...@linuxdriverproject.org; o...@aepfle.de; > a...@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? -- Jake Oshins _______________________________________________ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
