linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 215361] SL-6000 zaurus USB error - 'bad CDC descriptors'
Date: Fri, 28 Jan 2022 23:52:20 +0000	[thread overview]
Message-ID: <bug-215361-208809-nsWF7IAxAK@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215361-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=215361

--- Comment #12 from Ross Maynard (bids.7405@bigpond.com) ---
Hi Oliver,

I applied the patch, and was able to ping and ssh into my SL-6000.

Thanks!

On 28/1/22 2:50 am, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=215361
>
> --- Comment #11 from Oliver Neukum (oliver@neukum.org) ---
> Created attachment 300340
>    --> https://bugzilla.kernel.org/attachment.cgi?id=300340&action=edit
> another special case
>
> Please try this patch
>

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2022-01-28 23:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-19  6:14 [Bug 215361] New: SL-6000 zaurus USB error - 'bad CDC descriptors' bugzilla-daemon
2021-12-19 20:46 ` [Bug 215361] " bugzilla-daemon
2021-12-19 22:27 ` bugzilla-daemon
2021-12-20  8:37 ` [Bug 215361] New: " Greg KH
2021-12-20  8:37 ` [Bug 215361] " bugzilla-daemon
2021-12-21  8:07 ` bugzilla-daemon
2021-12-21  8:20   ` Greg KH
2021-12-21  8:20 ` bugzilla-daemon
2022-01-16  4:23 ` bugzilla-daemon
2022-01-26 12:31   ` Greg KH
2022-01-26 12:32 ` bugzilla-daemon
2022-01-27  2:25 ` bugzilla-daemon
2022-01-27  6:00 ` bugzilla-daemon
2022-01-27  7:45 ` bugzilla-daemon
2022-01-27 15:50 ` bugzilla-daemon
2022-01-28 23:52 ` bugzilla-daemon [this message]
2022-04-22  4:00 ` bugzilla-daemon

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=bug-215361-208809-nsWF7IAxAK@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --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).