linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "zhongling0719@126.com" <zhongling0719@126.com>
To: gregkh <gregkh@linuxfoundation.org>
Cc: zenghongling <zenghongling@kylinos.cn>,
	stern <stern@rowland.harvard.edu>,
	linux-usb <linux-usb@vger.kernel.org>,
	usb-storage <usb-storage@lists.one-eyed-alien.net>
Subject: Re: Re: [PATCH v4] uas: add no-uas quirk for Thinkplus and Hiksemi usb-storage
Date: Thu, 1 Sep 2022 21:58:03 +0800	[thread overview]
Message-ID: <2022090121570194160929@126.com> (raw)
In-Reply-To: YxCtyOUkRlIqcC4d@kroah.com

Some UASP capable USB-to-SATA bridge controllers are not compatible,this problem has always existed. you can refer to
other auther submit the similar patch. this patch is fixed no speed,not slow speed.

Thanks!  

zhongling0719@126.com
 
From: gregkh
Date: 2022-09-01 21:04
To: zhongling0719@126.com
CC: zenghongling; stern; linux-usb; usb-storage
Subject: Re: Re: [PATCH v4] uas: add no-uas quirk for Thinkplus and Hiksemi usb-storage
On Thu, Sep 01, 2022 at 08:38:21PM +0800, zhongling0719@126.com wrote:
> Hi:
>    Sorry again, The last email was wrong, fixed my email to not send html email and respond again. 
>    The drivers manufacturers advertised high speed support platform is Windows,MacOSX, not include linux 4.9 , this bug will affect the users 
> normal use, run iozone is just one of the behaviors that trigger UAS crash ,We will handle that slow issue.
 
I do not understand, sorry.
 
What is special about Linux that causes these drives to break with the
UAS protocol?  What is it doing different that OSX and Windows does not
do?
 
We should fix that bug, not degrade the performance of these devices to
extremely slow levels for no good reason.
 
thanks,
 
greg k-h

  reply	other threads:[~2022-09-01 13:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01  7:00 [PATCH v4] uas: add no-uas quirk for Thinkplus and Hiksemi usb-storage zenghongling
2022-09-01  8:37 ` Greg KH
     [not found]   ` <409cbf8b.5b1a.182f8682364.Coremail.zhongling0719@126.com>
2022-09-01 10:02     ` Greg KH
     [not found]       ` <202209012012228283526@126.com>
2022-09-01 12:33         ` gregkh
2022-09-01 12:38   ` zhongling0719
2022-09-01 13:04     ` gregkh
2022-09-01 13:58       ` zhongling0719 [this message]
2022-09-01 14:32         ` gregkh
2022-09-01 15:21           ` zhongling0719
2022-09-02  6:30           ` nana
2022-09-02  9:04             ` nana

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=2022090121570194160929@126.com \
    --to=zhongling0719@126.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=usb-storage@lists.one-eyed-alien.net \
    --cc=zenghongling@kylinos.cn \
    /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).