From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94249] libdrm_amdgpu: Crash when built with clang
Date: Tue, 02 Aug 2016 09:49:29 +0000 [thread overview]
Message-ID: <bug-94249-502-JMi8W7dGeP@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-94249-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 406 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=94249
--- Comment #14 from Michel Dänzer <michel@daenzer.net> ---
Created attachment 125478
--> https://bugs.freedesktop.org/attachment.cgi?id=125478&action=edit
Make sure the second argument to container_of() is initialized
Does this patch fix the problem with clang?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1478 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-08-02 9:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 15:58 [Bug 94249] Linux incorrectly detects a Radeon GPU bugzilla-daemon
2016-02-22 16:15 ` [Bug 94249] Topaz GPU not working correctly bugzilla-daemon
2016-03-01 15:31 ` bugzilla-daemon
2016-04-14 16:31 ` bugzilla-daemon
2016-07-29 6:35 ` bugzilla-daemon
2016-07-29 14:28 ` bugzilla-daemon
2016-07-29 14:30 ` bugzilla-daemon
2016-07-29 14:31 ` bugzilla-daemon
2016-07-29 14:32 ` bugzilla-daemon
2016-07-29 14:34 ` bugzilla-daemon
2016-07-30 15:04 ` bugzilla-daemon
2016-08-02 9:33 ` bugzilla-daemon
2016-08-02 9:37 ` bugzilla-daemon
2016-08-02 9:44 ` [Bug 94249] libdrm_amdgpu: Crash when built with clang bugzilla-daemon
2016-08-02 9:49 ` bugzilla-daemon [this message]
2016-08-02 10:04 ` bugzilla-daemon
2016-08-03 9:38 ` 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-94249-502-JMi8W7dGeP@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).