From: Greg KH <gregkh@linuxfoundation.org>
To: Dmytro Bagrii <dimich.dmb@gmail.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: core: Call disconnect() only if it is provided by driver
Date: Thu, 19 May 2022 15:45:58 +0200 [thread overview]
Message-ID: <YoZKFrzirES9+f39@kroah.com> (raw)
In-Reply-To: <20220519132900.4392-1-dimich.dmb@gmail.com>
On Thu, May 19, 2022 at 04:29:00PM +0300, Dmytro Bagrii wrote:
> A driver may use devres allocations. Disconnect handler is not needed in
> this case. Allow such driver to leave .disconnect field uninitialized in
> struct usb_driver instead of providing empty stub function.
>
> Signed-off-by: Dmytro Bagrii <dimich.dmb@gmail.com>
> ---
> drivers/usb/core/driver.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/usb/core/driver.c b/drivers/usb/core/driver.c
> index 355ed33a2179..d7fe440b033c 100644
> --- a/drivers/usb/core/driver.c
> +++ b/drivers/usb/core/driver.c
> @@ -455,7 +455,8 @@ static int usb_unbind_interface(struct device *dev)
> if (!driver->soft_unbind || udev->state == USB_STATE_NOTATTACHED)
> usb_disable_interface(udev, intf, false);
>
> - driver->disconnect(intf);
> + if (driver->disconnect)
> + driver->disconnect(intf);
>
> /* Free streams */
> for (i = 0, j = 0; i < intf->cur_altsetting->desc.bNumEndpoints; i++) {
> --
> 2.36.1
>
What in-kernel driver has this issue and does not have a disconnect
callback?
thanks,
greg k-h
next prev parent reply other threads:[~2022-05-19 13:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 13:29 [PATCH] usb: core: Call disconnect() only if it is provided by driver Dmytro Bagrii
2022-05-19 13:45 ` Greg KH [this message]
2022-05-19 15:27 ` Dmytro Bagrii
2022-05-19 16:38 ` Greg KH
2022-05-19 17:13 ` Dmytro Bagrii
2022-05-19 13:49 ` Alan Stern
2022-05-19 14:12 ` Oliver Neukum
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=YoZKFrzirES9+f39@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dimich.dmb@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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