From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 216745] Kernel 6.1 breaks Thinkpad T14 Gen 2 AMD connection to USB-C dock Gen 2 with kernel Null pointer
Date: Sat, 26 Nov 2022 21:54:45 +0000 [thread overview]
Message-ID: <bug-216745-2300-LV15Cn20AB@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216745-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216745
--- Comment #1 from Eric Zou (ezou@outlook.com) ---
I have a feeling that this bug shall actually be directly filed to
https://gitlab.freedesktop.org/drm/amd
instead of here, but I am not sure.
Thanks.
Eric
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-11-26 21:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 21:51 [Bug 216745] New: Kernel 6.1 breaks Thinkpad T14 Gen 2 AMD connection to USB-C dock Gen 2 with kernel Null pointer bugzilla-daemon
2022-11-26 21:54 ` bugzilla-daemon [this message]
2022-11-27 12:46 ` [Bug 216745] " bugzilla-daemon
2022-11-27 13:00 ` bugzilla-daemon
2022-11-27 23:14 ` bugzilla-daemon
2022-11-28 4:12 ` bugzilla-daemon
2022-11-28 8:31 ` 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-216745-2300-LV15Cn20AB@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=dri-devel@lists.freedesktop.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