All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: oushixiong <oushixiong1025@163.com>
Cc: Michael Grzeschik <m.grzeschik@pengutronix.de>,
	Sabyrzhan Tasbolatov <snovitoll@gmail.com>,
	Frederic Weisbecker <frederic@kernel.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	Xu Yang <xu.yang_2@nxp.com>, Al Viro <viro@zeniv.linux.org.uk>,
	Shixiong Ou <oushixiong@kylinos.cn>
Subject: Re: [PATCH] usb: gadget: uvc: destroy worker when function is unbound
Date: Sun, 20 Jul 2025 13:41:18 +0200	[thread overview]
Message-ID: <2025072007-undoing-tingle-3b35@gregkh> (raw)
In-Reply-To: <2025071129-subarctic-uniformly-8ae3@gregkh>

On Fri, Jul 11, 2025 at 05:30:52PM +0200, Greg Kroah-Hartman wrote:
> On Fri, Jul 11, 2025 at 11:29:36PM +0800, oushixiong wrote:
> > 
> > 在 2025/7/11 19:04, Greg Kroah-Hartman 写道:
> > > On Fri, Jul 11, 2025 at 04:35:50PM +0800,oushixiong1025@163.com wrote:
> > > > From: Shixiong Ou<oushixiong@kylinos.cn>
> > > > 
> > > > Destroy worker when function is unbound.
> > > This says what you did, but not why.
> > > 
> > > Why is this needed?  What happens without this change applied?
> > 
> > I think the kthread_worker created in uvcg_video_init() is not being
> > properly destroyed during the unbind phase.
> 
> Is this actually happening?  How was this noticed?  How was this tested?

Dropping from my review queue due to lack of response :(

      reply	other threads:[~2025-07-20 11:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-11  8:35 [PATCH] usb: gadget: uvc: destroy worker when function is unbound oushixiong1025
2025-07-11 11:04 ` Greg Kroah-Hartman
     [not found]   ` <d430ec08-70c0-4d2a-81aa-234e8f759cfc@163.com>
2025-07-11 15:30     ` Greg Kroah-Hartman
2025-07-20 11:41       ` Greg Kroah-Hartman [this message]

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=2025072007-undoing-tingle-3b35@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=m.grzeschik@pengutronix.de \
    --cc=oushixiong1025@163.com \
    --cc=oushixiong@kylinos.cn \
    --cc=snovitoll@gmail.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=xu.yang_2@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.