From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 85207] agd5f drm-next-3.19-wip + Unreal Elemental sometimes = list_add corruption/hung task
Date: Thu, 30 Oct 2014 09:55:05 +0000 [thread overview]
Message-ID: <bug-85207-502-FhIDIp0qdZ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-85207-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 467 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=85207
--- Comment #9 from Andy Furniss <adf.lists@gmail.com> ---
(In reply to Christian König from comment #6)
> But first things first, is the original issue with the list corruption
> fixed? If yes we can start to look into this one as well.
Enough time has passed now, so I do think that the patch fixed the list
corruption.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1395 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-10-30 9:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 21:07 [Bug 85207] New: agd5f drm-next-3.19-wip + Unreal Elemental sometimes = list_add corruption/hung task bugzilla-daemon
2014-10-19 21:14 ` [Bug 85207] " bugzilla-daemon
2014-10-20 9:21 ` bugzilla-daemon
2014-10-20 17:13 ` bugzilla-daemon
2014-10-21 9:54 ` bugzilla-daemon
2014-10-21 13:11 ` bugzilla-daemon
2014-10-22 13:45 ` bugzilla-daemon
2014-10-23 9:03 ` bugzilla-daemon
2014-10-23 22:17 ` bugzilla-daemon
2014-10-30 9:55 ` bugzilla-daemon [this message]
2014-12-30 9:54 ` bugzilla-daemon
2015-01-08 2:00 ` bugzilla-daemon
2015-01-08 15:48 ` bugzilla-daemon
2015-01-08 15:48 ` bugzilla-daemon
2015-07-30 11:49 ` bugzilla-daemon
2015-08-02 11:40 ` bugzilla-daemon
2015-08-02 11: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-85207-502-FhIDIp0qdZ@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