From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 212101] xhci_hcd cant setup
Date: Tue, 23 Mar 2021 06:44:47 +0000 [thread overview]
Message-ID: <bug-212101-208809-NfTv4YRrb1@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-212101-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=212101
pik a-b (hose@posteo.net) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from pik a-b (hose@posteo.net) ---
It seems now to me now that I mixed up to issues with tow different pieces of
hardware into one ticket. In general I am not sure how to gather the relevant
information needed for further analysis. Therefore, I recall this ticket.
pikab
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2021-03-23 6:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 12:28 [Bug 212101] New: xhci_hcd cant setup bugzilla-daemon
2021-03-13 9:01 ` [Bug 212101] " bugzilla-daemon
2021-03-23 6:44 ` bugzilla-daemon [this message]
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-212101-208809-NfTv4YRrb1@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).