On Tue, Feb 03, 2015 at 11:57:18PM +0000, KY Srinivasan wrote: > > > > -----Original Message----- > > From: Greg KH [mailto:gregkh@xxxxxxxxxxxxxxxxxxx] > > Sent: Tuesday, February 3, 2015 3:47 PM > > To: KY Srinivasan > > Cc: linux-kernel@xxxxxxxxxxxxxxx; devel@xxxxxxxxxxxxxxxxxxxxxx; > > olaf@xxxxxxxxx; apw@xxxxxxxxxxxxx; vkuznets@xxxxxxxxxx; > > tglx@xxxxxxxxxxxxx > > Subject: Re: [PATCH RESEND V2 0/8] Drivers: hv: vmbus: Enable unloading of > > vmbus driver > > > > On Wed, Jan 28, 2015 at 04:49:20PM -0800, K. Y. Srinivasan wrote: > > > Windows hosts starting with Ws2012 R2 permit re-establishing the vmbus > > > connection from the guest. This patch-set includes patches from Vitaly > > > to cleanup the VMBUS unload path so we can potentially reload the driver. > > > > > > This set also includes a patch from Jake to correctly extract MMIO > > > information on both Gen1 and Gen 2 firmware. > > > > What changed from v1 of this series? > > > > Please refresh your patch series and send _all_ patches that need to be > > applied, I see 2 different series, and a few random patches sent out, with no > > specific order, so I don't know what to do here :( > > > Ok; I will resend the entire set. Do you want me to keep the RESEND tag. If you use the "vX" numbering scheme, it doesn't make much sense, right? thanks, greg k-h _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
