> -----Original Message----- > From: gregkh@xxxxxxxxxxxxxxxxxxx [mailto:gregkh@xxxxxxxxxxxxxxxxxxx] > Sent: Thursday, January 26, 2017 2:28 AM > To: Dexuan Cui <decui@xxxxxxxxxxxxx> > Cc: Stephen Hemminger <stephen@xxxxxxxxxxxxxxxxxx>; driverdev- > devel@xxxxxxxxxxxxxxxxxxxxxx; KY Srinivasan <kys@xxxxxxxxxxxxx>; Haiyang > Zhang <haiyangz@xxxxxxxxxxxxx>; Stephen Hemminger > <sthemmin@xxxxxxxxxxxxx>; olaf@xxxxxxxxx; Rolf Neugebauer > <rolf.neugebauer@xxxxxxxxxx>; jasowang@xxxxxxxxxx; linux- > kernel@xxxxxxxxxxxxxxx; apw@xxxxxxxxxxxxx > Subject: Re: [PATCH] Drivers: hv: vmbus: finally fix > hv_need_to_signal_on_read() > > On Thu, Jan 26, 2017 at 10:24:32AM +0000, Dexuan Cui wrote: > > > From: gregkh@xxxxxxxxxxxxxxxxxxx [mailto:gregkh@xxxxxxxxxxxxxxxxxxx] > > > To: Dexuan Cui <decui@xxxxxxxxxxxxx> > > > > > > > > v4.4.44 needs 2 patches, i.e. a389fcfd2cb5, and this patch (which is not > in > > > > Linus's tree yet). Only backporting the first patch immediately is not > enough > > > > and is also improper IMO, because the first patch introduces a new > issue, > > > > which is being resolved by this patch. So my understanding is that I > should > > > > backport the 2 patches together. > > > > > > Ok, that makes a bit more sense, thanks. I'll wait for your "real" > > > patch to hit Linus's tree then. > > > > > > greg k-h > > > > Hi Greg, > > I expect this patch (i.e. the "real" patch) would go in your char-misc tree > first, > > then it would be merged into Linus's tree, as we usually did. > > That's fine, I'll wait for the maintainer of the subsystem to forward it > on to me, like all other hyperv patches :) I am putting together a set that I will be forwarding that includes this patch. K. Y > > Or, at the very least, have one of them ack it so that I can take it... > > thanks, > > greg k-hmu > > > > > IMO this is an important fix, but it's not so urgent that Linus would notice > > it and pick it up directly. > > > > Thanks, > > -- Dexuan _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
