From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 64801] KMS/R7xx - [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!
Date: Wed, 22 May 2013 20:40:42 +0000 [thread overview]
Message-ID: <bug-64801-502-J2gE9UvVFH@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-64801-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 235 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=64801
--- Comment #4 from Philip Prindeville <philipp@redfish-solutions.com> ---
Do I need to add anything else?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1070 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:[~2013-05-22 20:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-64801-502@http.bugs.freedesktop.org/>
2013-05-20 22:35 ` [Bug 64801] Seeing repeatable DRM relocation error messages with RV710 board bugzilla-daemon
2013-05-20 22:40 ` [Bug 64801] KMS/R100 - [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! bugzilla-daemon
2013-05-20 22:46 ` bugzilla-daemon
2013-05-20 22:48 ` [Bug 64801] KMS/R7xx " bugzilla-daemon
2013-05-20 22:51 ` bugzilla-daemon
2013-05-22 20:40 ` bugzilla-daemon [this message]
2013-05-23 0:00 ` bugzilla-daemon
2013-05-24 1:46 ` bugzilla-daemon
2013-05-24 8:00 ` bugzilla-daemon
2013-05-24 17:13 ` bugzilla-daemon
2013-05-25 1:27 ` bugzilla-daemon
2013-05-25 1:43 ` bugzilla-daemon
2013-11-30 21:58 ` bugzilla-daemon
2013-12-02 18:08 ` bugzilla-daemon
2013-12-02 19:02 ` bugzilla-daemon
2013-12-02 19:10 ` bugzilla-daemon
2013-12-24 0:23 ` bugzilla-daemon
2019-11-19 8:32 ` 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-64801-502-J2gE9UvVFH@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).