[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DM2PR0301MB12325FF8A5717BC1D75F038CABA60@DM2PR0301MB1232.namprd03.prod.outlook.com>
Date: Wed, 17 Jun 2015 17:41:58 +0000
From: Jake Oshins <jakeo@...rosoft.com>
To: Vitaly Kuznetsov <vkuznets@...hat.com>
CC: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
KY Srinivasan <kys@...rosoft.com>,
"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>,
Haiyang Zhang <haiyangz@...rosoft.com>,
Mike Ebersol <Michael.Ebersol@...rosoft.com>
Subject: RE: [PATCH v3 1/6] hv: Modify vmbus to search for all MMIO ranges
available
> -----Original Message-----
> From: Vitaly Kuznetsov [mailto:vkuznets@...hat.com]
> Sent: Wednesday, June 17, 2015 10:28 AM
> To: Jake Oshins
> Cc: gregkh@...uxfoundation.org; KY Srinivasan; linux-
> kernel@...r.kernel.org; devel@...uxdriverproject.org; olaf@...fle.de;
> apw@...onical.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
--
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