From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 217237] Fail to read EDID after resuming from suspend since kernel 6.2
Date: Fri, 24 Mar 2023 07:43:13 +0000 [thread overview]
Message-ID: <bug-217237-2300-nR9tDRLEF4@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217237-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217237
Artem S. Tashkinov (aros@gmx.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |ANSWERED
--- Comment #1 from Artem S. Tashkinov (aros@gmx.com) ---
Please report here instead https://gitlab.freedesktop.org/drm/amd/-/issues
Also, since you're not averse to testing, you could perform regression testing:
https://docs.kernel.org/admin-guide/bug-bisect.html
--
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:[~2023-03-24 7:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 21:40 [Bug 217237] New: Fail to read EDID after resuming from suspend since kernel 6.2 bugzilla-daemon
2023-03-24 7:43 ` bugzilla-daemon [this message]
2023-03-24 8:04 ` [Bug 217237] " 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-217237-2300-nR9tDRLEF4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.