From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 96625] GPU lockup when using r600g VDPAU on powerpc
Date: Thu, 23 Jun 2016 08:00:17 +0000 [thread overview]
Message-ID: <bug-96625-502-dITsYa5zuA@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-96625-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 503 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=96625
--- Comment #5 from Daniel Stone <daniel@fooishbar.org> ---
Mathieu - I don't work for AMD or any related company, but I can tell you that
demanding engineers provide position statements on behalf of 10,000-employee
companies isn't going to work. Christian is an engineer who is just working to
improve open source, and you're putting him in a very unfair position.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1275 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-06-23 8:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 23:49 [Bug 96625] GPU lockup when using r600g VDPAU on powerpc bugzilla-daemon
2016-06-22 7:22 ` bugzilla-daemon
2016-06-22 11:00 ` bugzilla-daemon
2016-06-22 11:08 ` bugzilla-daemon
2016-06-22 13:11 ` bugzilla-daemon
2016-06-23 7:56 ` bugzilla-daemon
2016-06-23 8:00 ` bugzilla-daemon [this message]
2016-06-23 8:29 ` bugzilla-daemon
2016-06-23 8:45 ` bugzilla-daemon
2016-06-23 13:29 ` bugzilla-daemon
2016-06-23 14:37 ` bugzilla-daemon
2016-06-23 15:21 ` bugzilla-daemon
2019-09-18 19:21 ` 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-96625-502-dITsYa5zuA@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).