From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93928] Tonga valley regression since drm/amdgpu: split VM mappings into smaller operations (v2)
Date: Fri, 29 Jan 2016 16:16:16 +0000 [thread overview]
Message-ID: <bug-93928-502-wSam7n8NUX@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93928-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 468 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93928
--- Comment #2 from Christian König <deathsimple@vodafone.de> ---
Crap, that looks like I haven't pushed the latest version of that to our server
where Alex picket it up. There are numerous bugs in the version of the patch
which went upstream.
I'm going to take a look what went wrong as soon as I have time (going to
FOSDEM this weekend).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1318 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:[~2016-01-29 16:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 14:48 [Bug 93928] Tonga valley regression since drm/amdgpu: split VM mappings into smaller operations (v2) bugzilla-daemon
2016-01-29 15:30 ` bugzilla-daemon
2016-01-29 16:16 ` bugzilla-daemon [this message]
2016-01-29 16:20 ` bugzilla-daemon
2016-01-29 17:11 ` bugzilla-daemon
2016-01-29 17:12 ` bugzilla-daemon
2016-01-30 10:06 ` bugzilla-daemon
2016-01-30 10:55 ` bugzilla-daemon
2016-05-02 22:48 ` 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-93928-502-wSam7n8NUX@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