From: Greg KH <gregkh@linuxfoundation.org>
To: Hu Xiaoying <huxiaoying2008@gmail.com>
Cc: usb-storage@lists.one-eyed-alien.net, linux-usb@vger.kernel.org,
stern@rowland.harvard.edu
Subject: Re: Confirmation for subscribe linux-usb
Date: Wed, 24 Aug 2022 13:49:59 +0200 [thread overview]
Message-ID: <YwYQZ/3Nf2hMKcHO@kroah.com> (raw)
In-Reply-To: <CABd4UjaBog_VVcYjc2YDTq3Q-cfSWVzVbRbffJr8i_YE8dh-nQ@mail.gmail.com>
On Wed, Aug 24, 2022 at 05:45:49PM +0800, Hu Xiaoying wrote:
> >From 040e7ed7e6e9ed850575ed075e02d960a5ffe191 Mon Sep 17 00:00:00 2001
Please stop and take a break for a day.
Look at the subject line of your email, is that what the other subject
lines for this mailing list look like? You can see all of the prior
emails on the list on lore.kernel.org if you want some examples.
> From: Hu Xiaoying <huxiaoying@kylinos.cn>
Ok, but this does not match your signed-off-by line, as my bot told you
to fix, why not?
> Date: Wed, 22 Jun 2022 16:35:59 +0800
> Subject: [PATCH -next] KYLIN: usb: Improves USB2.0 write performance for
> External HDD device (VID:PID = 0x0b05:0x1932)
That is a very long subject line, your editor told you to only use 50 or
so characters, please follow that rule.
>
> CVE: NA
Why is this even here at all? We don't track CVE numbers for kernel
patches, that's crazy and insane and even MITRE agrees that CVEs do not
make any sense at all for the Linux kernel. So don't even attempt to
classify something as "no CVE here" as that makes no sense.
>
> USB external storage device(0x0b05:1932), use gnome-disk-utility tools
> to test usb write < 30MB/s.
> then, igoned to load module of uas for this device.
> ===============================================
> Write speed: Improves form 27MB/s to 40MB/s+
That seems very odd, what about the USB 3 connection for this device?
Why is UAS so slow for this specific device?
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Hu Xiaoying <huxiaoying2008@gmail.cn>
> ---
> drivers/usb/storage/unusual_uas.h | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/usb/storage/unusual_uas.h
> b/drivers/usb/storage/unusual_uas.h
> index 4051c8cd0cd8..abaf4ea8138b 100644
> --- a/drivers/usb/storage/unusual_uas.h
> +++ b/drivers/usb/storage/unusual_uas.h
> @@ -157,3 +157,10 @@ UNUSUAL_DEV(0x4971, 0x8024, 0x0000, 0x9999,
> "External HDD",
> USB_SC_DEVICE, USB_PR_DEVICE, NULL,
> US_FL_ALWAYS_SYNC),
> +
> +/* Reported-by: Tom Hu <huxiaoying@kylinos.cn> */
> +UNUSUAL_DEV(0x0b05, 0x1932, 0x0000, 0x9999,
Why all versions? Why not just your one specific one?
Also, your patch is corrupted and can not be applied at all :(
Please take a day off, relax, and come back in a few days and resubmit a
fixed up commit after reading our documentation for how to properly
write and submit a kernel change.
thanks,
greg k-h
prev parent reply other threads:[~2022-08-24 11:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S240916AbiHWHMh/20220823071237Z+20120@vger.kernel.org>
[not found] ` <CABd4Uja9SoHpiMr2gDFcEP2Cudp7dcWJ_2i+KTEse9CU=KMtzw@mail.gmail.com>
[not found] ` <CABd4UjYB=nzha=eoogNJU4pFwW9+4PQ65bC5u=R-gCE_ZLSQXw@mail.gmail.com>
2022-08-24 6:59 ` Confirmation for subscribe linux-usb Greg KH
[not found] ` <CABd4UjaBog_VVcYjc2YDTq3Q-cfSWVzVbRbffJr8i_YE8dh-nQ@mail.gmail.com>
2022-08-24 11:49 ` 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=YwYQZ/3Nf2hMKcHO@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=huxiaoying2008@gmail.com \
--cc=linux-usb@vger.kernel.org \
--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