dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 217278] ast 0000:03:00.0: PM: **** DPM device timeout **** during S4 resuming
Date: Sun, 02 Apr 2023 08:15:03 +0000	[thread overview]
Message-ID: <bug-217278-2300-avMZuNq9Rj@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217278-2300@https.bugzilla.kernel.org/>

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

The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|regressions@leemhuis.info   |

--- Comment #7 from The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) ---
Then it sounds like this is not a regression and thus nothing for me.

But FWIW, I doubt your report here will reach the maintainers of the driver.
You might want to contact them by mail to Joel Stanley <joel@jms.id.au>, CCed
to linux-aspeed@lists.ozlabs.org

-- 
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:[~2023-04-02  8:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31  1:43 [Bug 217278] New: ast 0000:03:00.0: PM: **** DPM device timeout **** during S4 resuming bugzilla-daemon
2023-03-31  5:33 ` [Bug 217278] " bugzilla-daemon
2023-03-31  9:14 ` bugzilla-daemon
2023-04-02  2:53 ` bugzilla-daemon
2023-04-02  2:54 ` bugzilla-daemon
2023-04-02  2:54 ` bugzilla-daemon
2023-04-02  2:55 ` bugzilla-daemon
2023-04-02  8:15 ` bugzilla-daemon [this message]
2023-04-14  3:43 ` bugzilla-daemon
2023-04-14  3:47 ` bugzilla-daemon
2023-04-19  3:11 ` 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-217278-2300-avMZuNq9Rj@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;
as well as URLs for NNTP newsgroup(s).