From: Greg KH <gregkh@linuxfoundation.org>
To: Olivier Tuchon <tcn@google.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] usb: gadget: Address review comments and include missing files
Date: Sat, 26 Jul 2025 08:39:51 +0200 [thread overview]
Message-ID: <2025072652-chewable-stupor-9a4d@gregkh> (raw)
In-Reply-To: <CALU+5Vb8kFrR_HMOrBDktxEEQE4d4qBTijVpSdSQz4d3qXsfJQ@mail.gmail.com>
On Fri, Jul 25, 2025 at 11:09:26PM +0200, Olivier Tuchon wrote:
> This patch addresses feedback on v1 from greg k-h and Alan Stern. It
> also includes files that were missing from the initial submission.
>
> The following changes have been made:
> - correct initial coding style issue (spaces for tabs)
> - add missing file required for the feature to build and run
> - improve FIFO full handling by truncating event data instead of
> dropping the event entirely
> - avoid capturing redundant data for IN submissions
This is not a proper way to write a subject line or comments at all.
Look at patches on the list and in the tree, nothing starts with
"address review comments", right?
Please go back and start again...
>
> Signed-off-by: Olivier Tuchon <tcn@google.com>
> ---
> drivers/usb/Kconfig | 2 +
> drivers/usb/Makefile | 1 +
> drivers/usb/gadget/udc/core.c | 78 +++++++++++++++++++++++++
> drivers/usb/gadget_mon/Kconfig | 20 +++----
> drivers/usb/gadget_mon/gadgetmon_main.c | 41 ++++++++-----
> include/linux/usb/gadget.h | 23 ++++++++
> 6 files changed, 141 insertions(+), 24 deletions(-)
Please read the in-kernel documentation about how to submit a kernel
patch, it should explain all of this, right? If not, please work with
someone in your group that knows how to create kernel patches, don't
require the community to do that kind of basic review/training for you.
thanks,
greg k-h
prev parent reply other threads:[~2025-07-26 6:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 21:09 [PATCH v2] usb: gadget: Address review comments and include missing files Olivier Tuchon
2025-07-26 6:39 ` Greg KH [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=2025072652-chewable-stupor-9a4d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=tcn@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).