> From: KY Srinivasan <k...@microsoft.com> > Sent: Friday, November 30, 2018 9:31 AM > > From: Dexuan Cui <de...@microsoft.com> > > Sent: Thursday, November 29, 2018 12:17 AM > > To: gre...@linuxfoundation.org > > Cc: KY Srinivasan <k...@microsoft.com>; Haiyang Zhang > > <haiya...@microsoft.com>; Stephen Hemminger > > <sthem...@microsoft.com>; linux-ker...@vger.kernel.org; > > de...@linuxdriverproject.org; a...@canonical.com; vkuznets > > <vkuzn...@redhat.com>; o...@aepfle.de; jasow...@redhat.com; Michael > > Kelley <mikel...@microsoft.com> > > Subject: RE: [PATCH] [repost] Drivers: hv: vmbus: Offload the handling of > > channels to two workqueues > > > > > From: gre...@linuxfoundation.org <gre...@linuxfoundation.org> > > > Sent: Wednesday, November 28, 2018 11:45 PM > > > > > > > > There is no change in this repost. I just rebased this patch to today's > > > > char-misc's char-misc-next branch. Previously KY posted the patch with > > his > > > > Signed-off-by (which is kept in this repost), but there was a conflict > > > > issue. > > > > > > > > Note: the patch can't be cleanly applied to char-misc's char-misc-linus > > branch > > > -- > > > > to do that, we need to cherry-pick the supporting patch first: > > > > 4d3c5c69191f ("Drivers: hv: vmbus: Remove the useless API > > > vmbus_get_outgoing_channel()") > > > > > > That is not going to work for the obvious reason that this dependant > > > patch is not going to be merged into 4.20-final. > > > > It looks the dependent patch (4d3c5c69191f) is going to miss the v4.20 > > release. > > This is not a big issue, as the dependent patch isn't really important. > > > > > So, what do you expect us to do here? The only way this can be accepted > > > is to have it go into my -next branch, which means it will show up in > > > 4.21-rc1, is that ok? > > > > Is there any chance for this patch ("Drivers: hv: vmbus: Offload the > > handling > > ...") to > > go into v4.20? > > > > If yes, I can quickly do a rebase to char-misc's char-misc-linus branch, > > because actually the conflict can be very easily fixed. And I can help to > > fix any > > conflict when the dependent patch is backported to v4.20.1. > > This patch fixes an important bug while the patch this depends on is not > critical. > I suggest we revert the patch that this patch depends on > and we can submit a new version of this patch that can go in now - into 4.20 > release. > > K. Y
I agree. Hi Greg, Please let us know what we can do to try to push this important fix into v4.20. Actually it's straightforward, though it looks big. And, we ave done a full testing with the patch. Thanks, --Dexuan _______________________________________________ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel