From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99143] r9 390: Hardware cursor invisible after hibernate/resume
Date: Tue, 20 Dec 2016 14:29:20 +0000 [thread overview]
Message-ID: <bug-99143-502-vWR8EQmVCn@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99143-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 558 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99143
--- Comment #3 from Michel Dänzer <michel@daenzer.net> ---
(In reply to Harald Judt from comment #2)
> Unfortunately, the commit does not fix the problem.
Just to make sure, you did update the drm-next-4.10-wip branch again before
testing, right? The commit in question only appeared there after you submitted
this report.
If that commit really doesn't fix the problem, can you bisect which commit
introduced it?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1444 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
next prev parent reply other threads:[~2016-12-20 14:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 14:12 [Bug 99143] r9 390: Hardware cursor invisible after hibernate/resume bugzilla-daemon
2016-12-20 2:10 ` bugzilla-daemon
2016-12-20 11:03 ` bugzilla-daemon
2016-12-20 14:29 ` bugzilla-daemon [this message]
2017-01-10 9:22 ` bugzilla-daemon
2017-01-10 10:02 ` bugzilla-daemon
2017-01-11 9:42 ` bugzilla-daemon
2017-01-13 9:46 ` bugzilla-daemon
2019-11-19 8: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-99143-502-vWR8EQmVCn@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox