From: Aditya Garg <gargaditya08@live.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "oneukum@suse.com" <oneukum@suse.com>,
"stern@rowland.harvard.edu" <stern@rowland.harvard.edu>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"usb-storage@lists.one-eyed-alien.net"
<usb-storage@lists.one-eyed-alien.net>,
Kerem Karabay <kekrby@gmail.com>,
Orlando Chamberlain <orlandoch.dev@gmail.com>
Subject: Re: [PATCH] USB: core: add 'shutdown' callback to usb_driver
Date: Sat, 6 Jul 2024 08:56:05 +0000 [thread overview]
Message-ID: <C5231A8D-C529-4BAC-9E2D-32F00321A294@live.com> (raw)
In-Reply-To: <2024070649-nuzzle-movable-f383@gregkh>
Hi Greg
> On 6 Jul 2024, at 1:43 PM, gregkh@linuxfoundation.org wrote:
>
> On Fri, Jul 05, 2024 at 11:21:06AM +0000, Aditya Garg wrote:
>> From: Kerem Karabay <kekrby@gmail.com>
>>
>> This simplifies running code on shutdown for USB drivers.
>>
>
> Sorry, but this does not explain why this is needed at all :(
>
> Where did this change come from? What problem does it solve? Why
> should we take it?
>
Currently there is no standardized method for USB drivers to handle
shutdown events. This patch simplifies running code on shutdown for USB
devices by adding a shutdown callback to usb_driver. It also implements the
new method to existing "USB Attached SCSI” driver that required shutdown
Is this good enough?
> I think I know the answers to these questions, but you need to document
> it here as to why it is needed (please read the kernel documentation for
> how to write a good changelog text and subject line.)
The subject looks fine to me. If you think it can be improved, suggestions shall be appreciated.
Thanks
Aditya
next prev parent reply other threads:[~2024-07-06 8:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 11:21 Aditya Garg
2024-07-05 11:22 ` Aditya Garg
2024-07-06 8:13 ` gregkh
2024-07-06 8:56 ` Aditya Garg [this message]
2024-07-06 9:02 ` gregkh
2024-07-06 9:04 ` Aditya Garg
2024-07-06 10:04 ` Aditya Garg
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=C5231A8D-C529-4BAC-9E2D-32F00321A294@live.com \
--to=gargaditya08@live.com \
--cc=gregkh@linuxfoundation.org \
--cc=kekrby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=orlandoch.dev@gmail.com \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@lists.one-eyed-alien.net \
/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
all inboxes | Powered by JetHome®