> -----Original Message----- > From: K. Y. Srinivasan [mailto:kys@xxxxxxxxxxxxx] > Sent: Thursday, May 23, 2013 3:02 PM > To: gregkh@xxxxxxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; > devel@xxxxxxxxxxxxxxxxxxxxxx; olaf@xxxxxxxxx; apw@xxxxxxxxxxxxx; > jasowang@xxxxxxxxxx > Cc: KY Srinivasan > Subject: [PATCH V2 0/2] Drivers: hv: vmbus: Implement multi-channel support > > This patch-set implements multi-channel support for Hyper-V devices. > > Earlier, these two patches were sent out as part of a larger patch-set > that included relevant changes in the storage driver. > > In this version of the patch, I have fixed a race condition in the code that > opens the sub-channels. > > K. Y. Srinivasan (2): > Drivers: hv: vmbus: Implement multi-channel support > Drivers: hv: Add the GUID fot synthetic fibre channel device > > drivers/hv/channel.c | 50 +++++++++++++++++-- > drivers/hv/channel_mgmt.c | 119 > +++++++++++++++++++++++++++++++++++++++++++-- > drivers/hv/connection.c | 14 +++++ > include/linux/hyperv.h | 70 ++++++++++++++++++++++++++ > 4 files changed, 245 insertions(+), 8 deletions(-) Greg, You had acked the previous version of these patches that I had sent along with the storage driver patches that used this infrastructure. We are going to be submitting network driver patches that will use this infrastructure to implement VRSS (virtual receive side scaling) and that is the reason I chose to not tie up these vmbus patches with the storvsc patches. Please let me know if you are ok with the changes I have made in this version. Once these patches are committed, we will submit both storage and networking patches that use this infrastructure. Regards, K. Y > > -- > 1.7.4.1 > > _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
