mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Aditya Garg <gargaditya08@live.com>
Cc: "oneukum@suse.com" <oneukum@suse.com>,
	"stern@rowland.harvard.edu" <stern@rowland.harvard.edu>,
	Kerem Karabay <kekrby@gmail.com>,
	Orlando Chamberlain <orlandoch.dev@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@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>
Subject: Re: [PATCH v3 1/2] USB: core: add 'shutdown' callback to usb_driver
Date: Sat, 6 Jul 2024 14:36:44 +0200	[thread overview]
Message-ID: <2024070612-squealer-wackiness-c885@gregkh> (raw)
In-Reply-To: <7AAC1BF4-8B60-448D-A3C1-B7E80330BE42@live.com>

On Sat, Jul 06, 2024 at 12:03:23PM +0000, Aditya Garg wrote:
> From: Kerem Karabay <kekrby@gmail.com>
> 
> 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.
> 
> Signed-off-by: Kerem Karabay <kekrby@gmail.com>

Where did Kerem do this work?  Any reason why they aren't submitting
these themselves?  Not that this is a problem, just trying to figure out
what went wrong with the development process here.

thanks,

greg k-h

  parent reply	other threads:[~2024-07-06 12:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-06 12:02 [PATCH v3 0/2] USB: Simplify running code on shutdown for USB devices Aditya Garg
2024-07-06 12:03 ` [PATCH v3 1/2] USB: core: add 'shutdown' callback to usb_driver Aditya Garg
2024-07-06 12:04   ` [PATCH v3 2/2] USB: uas: Implement the new shutdown callback Aditya Garg
2024-07-06 12:36   ` gregkh [this message]
2024-07-06 12:46     ` [PATCH v3 1/2] USB: core: add 'shutdown' callback to usb_driver Aditya Garg
2024-07-06 12:56       ` 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=2024070612-squealer-wackiness-c885@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=gargaditya08@live.com \
    --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®