linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: "Till Dörges" <doerges@pre-sense.de>
Cc: linux-usb@vger.kernel.org
Subject: Re: Ext. HDDs not working under Linux via USB 3.0 but under Windows
Date: Wed, 26 Aug 2020 10:28:52 -0400	[thread overview]
Message-ID: <20200826142852.GA400430@rowland.harvard.edu> (raw)
In-Reply-To: <0c7a4975-596e-9c5a-062f-df77e8ebe969@pre-sense.de>

On Wed, Aug 26, 2020 at 01:51:58PM +0200, Till Dörges wrote:
> Am 25.08.20 um 20:45 schrieb Alan Stern:
> > On Fri, Jun 19, 2020 at 08:01:57PM +0200, Till Dörges wrote:
> >> Am 19.06.20 um 17:05 schrieb Alan Stern:
> >>
> >>> Can you build and test a kernel with the patch below, to make sure it does 
> >>> what you want?
> >>
> >> I was afraid you might say that. ;-)
> >>
> >> I don't have a kernel dev environment handy (that was the main reason why I was happy
> >> with your offer of writing the patch).
> >>
> >> I'll try setting one up, but it may take a moment.
> > 
> > It has been a couple of months.  Did you make any progress on this?
> 
> 
> Thanks for the reminder and sorry for the delay.
> 
> 
> I just tested your patch and it works like a charm.
> 
> 
> Testing was performed on:
> 
> --- snip ---
> user@box:~> lsb-release -d
> Description:    openSUSE Leap 15.1
> 
> user@box:~> uname -a
> Linux box.none 4.12.14-lp151.28.59-default #1 SMP Wed Aug 5 10:58:34 UTC 2020
> (337e42e) x86_64 x86_64 x86_64 GNU/Linux
> --- snip ---
> 
> 
> against the Kernel distributed by openSUSE:
> 
> --- snip ---
> user@box:~> rpm -q kernel-source
> kernel-source-4.12.14-lp151.28.59.1.noarch
> --- snip ---
> 
> 
> The patch applied and after loading the new uas.ko the HDDs which didn't work before
> worked just fine.
> 
> 
> I understand the openSUSE Leap Kernel is somewhat different from Kernel HEAD but I'd
> assume that for the purpose of this test these differences are acceptable.
> 
> 
> Is there anything else I can do to help?

Nope, this is all set.  I'll go ahead and submit the patch.

Alan Stern

  reply	other threads:[~2020-08-26 14:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-23 14:57 Ext. HDDs not working under Linux via USB 3.0 but under Windows Till Dörges
2020-05-23 15:48 ` Alan Stern
2020-05-23 20:05   ` Till Dörges
2020-05-23 20:33     ` Alan Stern
2020-05-24  7:46       ` Till Dörges
2020-05-24 14:34         ` Alan Stern
2020-06-17 16:02       ` Till Dörges
2020-06-17 16:37         ` Alan Stern
2020-06-18  6:07           ` Till Dörges
2020-06-18  7:30             ` Till Dörges
2020-06-19 12:07               ` Till Dörges
2020-06-19 15:05                 ` Alan Stern
2020-06-19 18:01                   ` Till Dörges
2020-08-25 18:45                     ` Alan Stern
2020-08-26 11:51                       ` Till Dörges
2020-08-26 14:28                         ` Alan Stern [this message]
2020-08-26 14:32                         ` [PATCH] usb: storage: Add unusual_uas entry for Sony PSZ drives Alan Stern

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=20200826142852.GA400430@rowland.harvard.edu \
    --to=stern@rowland.harvard.edu \
    --cc=doerges@pre-sense.de \
    --cc=linux-usb@vger.kernel.org \
    /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).