> From: Greg KH [mailto:[email protected]]
> Sent: Monday, December 11, 2017 12:59 PM
> To: Dexuan Cui <[email protected]>
> Cc: Stephen Hemminger <[email protected]>; [email protected];
> Stephen Hemminger <[email protected]>; [email protected];
> [email protected]; [email protected]; [email protected];
> [email protected]; [email protected];
> [email protected]; [email protected]
> Subject: Re: [PATCH 1/2] vmbus: unregister device_obj->channels_kset
> 
> On Mon, Dec 11, 2017 at 08:41:44PM +0000, Dexuan Cui wrote:
> > > From: devel [mailto:[email protected]] On
> > > Behalf Of Stephen Hemminger
> > > Sent: Tuesday, November 28, 2017 9:30 AM
> > > To: Greg KH <[email protected]>
> > > Cc: [email protected]; Stephen Hemminger <[email protected]>;
> > > [email protected]; [email protected];
> [email protected];
> > > [email protected]; [email protected];
> > > [email protected]; [email protected];
> > > [email protected]
> > > Subject: Re: [PATCH 1/2] vmbus: unregister device_obj->channels_kset
> > >
> > > On Tue, 28 Nov 2017 16:56:05 +0100
> > > Greg KH <[email protected]> wrote:
> > >
> > > > On Tue, Nov 14, 2017 at 06:53:32AM -0700,
> [email protected]
> > > wrote:
> > > > > From: Dexuan Cui <[email protected]>
> > > > >
> > > > > Fixes: c2e5df616e1a ("vmbus: add per-channel sysfs info")
> > > > >
> > > > > Without the patch, a device can't be thoroughly destroyed, because
> > > > > vmbus_device_register() -> kset_create_and_add() still holds a 
> > > > > reference
> > > > > to the hv_device's device.kobj.
> > > > >
> > > > > Signed-off-by: Dexuan Cui <[email protected]>
> > > > > Cc: Stephen Hemminger <[email protected]>
> > > > > Cc: [email protected]
> > > >
> > > > Why is this marked for stable when the patch it "fixes" is in 4.15-rc1?
> > >
> > > It doesn't need to go to stable.
> >
> > Hi Greg,
> > May I know the status of the patch?
> 
> It's still in my "to-apply" queue.  As it's only a 4.15-final thing,
> don't worry, it will get there...
> 
> thanks,
> 
> greg k-h

Thanks a lot, Greg!

-- Dexuan
_______________________________________________
devel mailing list
[email protected]
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

Reply via email to