From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100577] DC + TearFree display lock
Date: Wed, 16 Aug 2017 12:54:42 +0000 [thread overview]
Message-ID: <bug-100577-502-KhngmieATl@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100577-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 596 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100577
Andy Furniss <adf.lists@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WORKSFORME
Status|NEW |RESOLVED
--- Comment #17 from Andy Furniss <adf.lists@gmail.com> ---
Testing with amd-staging-drm-next, which doesn't peg memclk high I can't
reproduce this anymore.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2043 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2017-08-16 12:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 10:52 [Bug 100577] DC + TearFree display lock bugzilla-daemon
2017-04-06 2:29 ` bugzilla-daemon
2017-05-04 9:08 ` bugzilla-daemon
2017-05-04 9:10 ` bugzilla-daemon
2017-05-06 17:54 ` bugzilla-daemon
2017-05-07 7:38 ` bugzilla-daemon
2017-05-16 21:47 ` bugzilla-daemon
2017-05-17 13:16 ` bugzilla-daemon
2017-05-17 22:17 ` bugzilla-daemon
2017-07-05 18:44 ` bugzilla-daemon
2017-07-05 18:59 ` bugzilla-daemon
2017-07-05 19:19 ` bugzilla-daemon
2017-07-05 20:01 ` bugzilla-daemon
2017-07-05 20:02 ` bugzilla-daemon
2017-07-05 20:03 ` bugzilla-daemon
2017-07-05 20:11 ` bugzilla-daemon
2017-07-05 20:37 ` bugzilla-daemon
2017-08-16 12:54 ` 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-100577-502-KhngmieATl@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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.