From: "Schmid, Carsten" <Carsten_Schmid@mentor.com>
To: Oliver Neukum <oneukum@suse.com>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: AW: AW: Strange behaviour of D-Link DUB-1312 USB 3.0 Adapters
Date: Fri, 16 Aug 2019 11:56:30 +0000 [thread overview]
Message-ID: <93de327cbfda4cbb930a83aa58274125@SVR-IES-MBX-03.mgc.mentorg.com> (raw)
In-Reply-To: <1565870525382.10504@mentor.com>
> >> I don't think its a regression.
> >
> > It would be better to know than to assume.
> >
> Happens with kernel 4.14.102 also, not only with 4.14.129.
> Looks more HW related.
>
Confirmed: HW issue.
Best regards
Carsten
next prev parent reply other threads:[~2019-08-16 11:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 8:17 Strange behaviour of D-Link DUB-1312 USB 3.0 Adapters Schmid, Carsten
2019-08-14 8:31 ` Oliver Neukum
2019-08-14 8:56 ` AW: " Schmid, Carsten
2019-08-14 10:22 ` Schmid, Carsten
2019-08-14 13:07 ` Oliver Neukum
2019-08-15 12:02 ` AW: " Schmid, Carsten
2019-08-16 11:56 ` Schmid, Carsten [this message]
2019-08-19 12:11 ` Oliver Neukum
2019-08-19 12:27 ` AW: " Schmid, Carsten
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=93de327cbfda4cbb930a83aa58274125@SVR-IES-MBX-03.mgc.mentorg.com \
--to=carsten_schmid@mentor.com \
--cc=f.fainelli@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.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).