All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 64810] EGL/Gles/Weston give segfault on RADEONSI with egl_gallium.so
Date: Tue, 14 Jan 2014 10:48:56 +0000	[thread overview]
Message-ID: <bug-64810-502-Kqktothaur@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-64810-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 757 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=64810

Marek Olšák <maraeo@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #35 from Marek Olšák <maraeo@gmail.com> ---
(In reply to comment #34)
> (In reply to comment #33)
> > Does this still happen with current Mesa Git master? There should no longer
> > be any symbol clashes between radeonsi and r600g.
> 
> Yes, fixed here with radeonsi and mesa-git

I'm closing this then.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2426 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

  parent reply	other threads:[~2014-01-14 10:48 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-21  4:58 [Bug 64810] New: EGL/Gles/Weston give segfault on RADEONSI bugzilla-daemon
2013-05-22 11:15 ` [Bug 64810] " bugzilla-daemon
2013-05-22 23:28 ` bugzilla-daemon
2013-05-23  7:33 ` [Bug 64810] EGL/Gles/Weston give segfault on RADEONSI with egl_gallium.so bugzilla-daemon
2013-05-23  7:35 ` bugzilla-daemon
2013-05-23 14:51 ` bugzilla-daemon
2013-05-23 15:31 ` bugzilla-daemon
2013-08-19 13:17 ` bugzilla-daemon
2013-08-22 14:55 ` bugzilla-daemon
2013-08-27 22:00 ` bugzilla-daemon
2013-08-28  1:08 ` bugzilla-daemon
2013-08-28  2:25 ` bugzilla-daemon
2013-08-28  7:51 ` bugzilla-daemon
2013-08-29 13:35 ` bugzilla-daemon
2013-08-29 13:40 ` bugzilla-daemon
2013-08-29 21:55 ` bugzilla-daemon
2013-08-29 23:51 ` bugzilla-daemon
2013-08-29 23:56 ` bugzilla-daemon
2013-08-30 16:36 ` bugzilla-daemon
2013-09-10 11:44 ` bugzilla-daemon
2013-09-18  2:03 ` bugzilla-daemon
2013-09-18  2:09 ` bugzilla-daemon
2013-09-18  2:46 ` bugzilla-daemon
2013-09-18  3:32 ` bugzilla-daemon
2013-09-18  3:47 ` bugzilla-daemon
2013-09-18  4:43 ` bugzilla-daemon
2013-09-20  1:09 ` bugzilla-daemon
2013-09-20 14:24 ` bugzilla-daemon
2013-09-20 23:44 ` bugzilla-daemon
2013-09-23 16:02 ` bugzilla-daemon
2013-11-03 12:48 ` bugzilla-daemon
2013-11-04 16:19 ` bugzilla-daemon
2014-01-12 22:13 ` bugzilla-daemon
2014-01-14  9:17 ` bugzilla-daemon
2014-01-14  9:52 ` bugzilla-daemon
2014-01-14 10:48 ` bugzilla-daemon [this message]
2014-01-14 12:20 ` bugzilla-daemon
2014-01-14 15:41 ` bugzilla-daemon
2014-01-15 23:17 ` 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-64810-502-Kqktothaur@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.