From: Greg KH <gregkh@linuxfoundation.org>
To: "stern@rowland.harvard.edu" <stern@rowland.harvard.edu>
Cc: "zhongling0719@126.com" <zhongling0719@126.com>,
"zenghongling@kylinos.cn" <zenghongling@kylinos.cn>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"usb-storage@lists.one-eyed-alien.net"
<usb-storage@lists.one-eyed-alien.net>
Subject: Re: Re: [PATCH v4 3/3] uas: ignore UAS for Thinkplus chips
Date: Fri, 9 Sep 2022 20:34:53 +0200 [thread overview]
Message-ID: <YxuHTRKC3Gv7cemF@kroah.com> (raw)
In-Reply-To: <YxuDzEdZX1zrIwOQ@rowland.harvard.edu>
On Fri, Sep 09, 2022 at 02:19:56PM -0400, stern@rowland.harvard.edu wrote:
> On Fri, Sep 09, 2022 at 09:22:25PM +0800, zhongling0719@126.com wrote:
> > Sorry , I tested it work well on Win7, not good on Win10.
>
> I would guess that Windows 7 doesn't use UAS but Windows 10 does. It's
> surprising that these devices can be sold nowadays if they don't work
> with Windows 10 -- who would buy them?
>
> > I don't have Mac OSX system. We always work on linux environment.
> > Need I resend the version V5 for patch 3 cancel "acked by" ?
>
> Greg, do you have an opinion? I don't feel very strongly about this.
I'm going to drop all of these now as they are not being sent properly
despite numerous requests to have them done so :(
So yes, if they want to be applied, we need another version.
But again, I find it very very hard to believe they do not work properly
on Windows 10/11/OSX as well as Windows 10 has been out for a very long
time now and no one would accept such poor performance on those devices.
thanks,
greg k-h
next prev parent reply other threads:[~2022-09-09 18:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 10:48 [PATCH v4 3/3] uas: ignore UAS for Thinkplus chips Hongling Zeng
2022-09-09 12:15 ` Alan Stern
2022-09-09 13:22 ` zhongling0719
2022-09-09 18:19 ` stern
2022-09-09 18:34 ` Greg KH [this message]
2022-09-10 1:04 ` zhongling0719
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=YxuHTRKC3Gv7cemF@kroah.com \
--to=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 \
--cc=zhongling0719@126.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