From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 80029] [bisected] HDMI Errors on drm-next & Linus's tree
Date: Mon, 16 Jun 2014 14:10:22 +0000 [thread overview]
Message-ID: <bug-80029-502-8tLJRNGk8l@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-80029-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 241 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=80029
--- Comment #19 from Alex Deucher <agd5f@yahoo.com> ---
I've added the fix to my drm-fixes tree. It is correct.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1019 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-06-16 14:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-14 17:06 [Bug 80029] New: [bisected] HDMI Errors on drm-next & Linus's tree bugzilla-daemon
2014-06-14 17:07 ` [Bug 80029] " bugzilla-daemon
2014-06-14 18:19 ` bugzilla-daemon
2014-06-14 18:50 ` bugzilla-daemon
2014-06-14 18:51 ` bugzilla-daemon
2014-06-15 15:30 ` bugzilla-daemon
2014-06-15 15:41 ` bugzilla-daemon
2014-06-15 16:23 ` bugzilla-daemon
2014-06-15 16:25 ` bugzilla-daemon
2014-06-15 16:45 ` bugzilla-daemon
2014-06-15 17:00 ` bugzilla-daemon
2014-06-15 17:01 ` bugzilla-daemon
2014-06-15 17:10 ` bugzilla-daemon
2014-06-15 18:41 ` bugzilla-daemon
2014-06-15 18:45 ` bugzilla-daemon
2014-06-15 18:50 ` bugzilla-daemon
2014-06-15 19:19 ` bugzilla-daemon
2014-06-15 19:32 ` bugzilla-daemon
2014-06-15 19:48 ` bugzilla-daemon
2014-06-16 14:10 ` bugzilla-daemon [this message]
2014-06-25 13:41 ` 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-80029-502-8tLJRNGk8l@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;
as well as URLs for NNTP newsgroup(s).