From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 206427] go7007 driver fails to handle interrupt
Date: Thu, 06 Feb 2020 15:34:46 +0000 [thread overview]
Message-ID: <bug-206427-208809-5gyTehZtm3@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206427-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206427
--- Comment #10 from Takashi Iwai (tiwai@suse.de) ---
Yes, the firmware loading mechanism went to the kernel module.
The kernel warning seems fixed by correcting the urb properly like the patch
below. I'll submit to upstream.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-02-06 15:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 12:24 [Bug 206427] New: go7007 driver fails to handle interrupt bugzilla-daemon
2020-02-05 12:29 ` Greg KH
2020-02-05 12:29 ` [Bug 206427] " bugzilla-daemon
2020-02-05 13:45 ` bugzilla-daemon
2020-02-05 13:57 ` bugzilla-daemon
2020-02-05 15:43 ` bugzilla-daemon
2020-02-06 9:27 ` bugzilla-daemon
2020-02-06 9:33 ` bugzilla-daemon
2020-02-06 10:00 ` bugzilla-daemon
2020-02-06 15:34 ` bugzilla-daemon [this message]
2020-02-06 15:43 ` 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-206427-208809-5gyTehZtm3@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).