From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Dexuan Cui <decui@microsoft.com>
Cc: KY Srinivasan <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"apw@canonical.com" <apw@canonical.com>,
vkuznets <vkuznets@redhat.com>, "olaf@aepfle.de" <olaf@aepfle.de>,
"jasowang@redhat.com" <jasowang@redhat.com>,
Michael Kelley <mikelley@microsoft.com>
Subject: Re: [PATCH] [repost] Drivers: hv: vmbus: Offload the handling of channels to two workqueues
Date: Sun, 2 Dec 2018 08:33:45 +0100 [thread overview]
Message-ID: <20181202073345.GC31761@kroah.com> (raw)
In-Reply-To: <PU1P153MB016907FDC34F47CFE71B82EABFD30@PU1P153MB0169.APCP153.PROD.OUTLOOK.COM>
On Fri, Nov 30, 2018 at 06:09:54PM +0000, Dexuan Cui wrote:
> > From: KY Srinivasan <kys@microsoft.com>
> > Sent: Friday, November 30, 2018 9:31 AM
> > > From: Dexuan Cui <decui@microsoft.com>
> > > Sent: Thursday, November 29, 2018 12:17 AM
> > > To: gregkh@linuxfoundation.org
> > > Cc: KY Srinivasan <kys@microsoft.com>; Haiyang Zhang
> > > <haiyangz@microsoft.com>; Stephen Hemminger
> > > <sthemmin@microsoft.com>; linux-kernel@vger.kernel.org;
> > > devel@linuxdriverproject.org; apw@canonical.com; vkuznets
> > > <vkuznets@redhat.com>; olaf@aepfle.de; jasowang@redhat.com; Michael
> > > Kelley <mikelley@microsoft.com>
> > > Subject: RE: [PATCH] [repost] Drivers: hv: vmbus: Offload the handling of
> > > channels to two workqueues
> > >
> > > > From: gregkh@linuxfoundation.org <gregkh@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.
Ok, you all need to figure this out on your own, sorry. Please give me
a patch that I can actually apply to the tree if you need it merged into
4.20-final. This shouldn't be tough, you all have been doing this long
enough by now...
I have no bandwidth to do this myself for you,
greg k-h
next prev parent reply other threads:[~2018-12-02 7:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 4:36 [PATCH] [repost] Drivers: hv: vmbus: Offload the handling of channels to two workqueues Dexuan Cui
2018-11-29 7:44 ` gregkh
2018-11-29 8:17 ` Dexuan Cui
2018-11-30 17:31 ` KY Srinivasan
2018-11-30 18:09 ` Dexuan Cui
2018-12-02 7:33 ` gregkh [this message]
2018-12-02 8:47 ` Dexuan Cui
2018-12-02 15:33 ` gregkh
2018-12-03 0:50 ` Dexuan Cui
2018-12-03 11:50 ` Dan Carpenter
2018-12-03 18:41 ` Dan Carpenter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181202073345.GC31761@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=apw@canonical.com \
--cc=decui@microsoft.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=olaf@aepfle.de \
--cc=sthemmin@microsoft.com \
--cc=vkuznets@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox