From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 119991] Screen is corrupt upon resume from hybrid-sleep with Radeon HD5xxx cards
Date: Mon, 13 Jun 2016 12:13:45 +0000 [thread overview]
Message-ID: <bug-119991-2300-AHI5PsWFRp@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-119991-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=119991
--- Comment #4 from Felix Schwarz <felix.schwarz@oss.schwarz.eu> ---
(In reply to Jani-Markus Maunus from comment #3)
> I might be just rambling at this point, but 4.6.1 stable was definitely
> bugged for me, yet this commit is dated well before 4.6.1 release - any idea
> what's up with that?
Well it seems to me as if Jérôme's patch was merged via Alex's 'drm-next' and
Dave's 'drm-next-4.7' branches so it just missed the boat for 4.6. Also the
commit you pointed out above has no "stable" tag so it won't be picked up
automatically for point releases.
If you really care about 4.6 you might want to ping the authors and/or the
reviewers who might be willing to nominate the patch for the stable series.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2016-06-13 12:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-11 2:41 [Bug 119991] New: Screen is corrupt upon resume from hybrid-sleep with Radeon HD5xxx cards bugzilla-daemon
2016-06-12 10:26 ` [Bug 119991] " bugzilla-daemon
2016-06-12 13:17 ` bugzilla-daemon
2016-06-13 7:20 ` bugzilla-daemon
2016-06-13 12:13 ` 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-119991-2300-AHI5PsWFRp@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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.