From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 48424] Fix warnings/errors reported by clang's scan-build tool
Date: Mon, 09 Apr 2012 14:30:44 +0000 [thread overview]
Message-ID: <bug-48424-502-YLAYdZNb3F@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-48424-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=48424
--- Comment #2 from Chad Versace <chad@chad-versace.us> 2012-04-09 14:30:44 UTC ---
Thanks for doing this. Here's my review of mesa/main/extensions.c.
mesa/main/extensions.c:730: Thanks. I just submitted a patch for this memory
leak. You're CC'd.
mesa/main/extensions.c:866: false positive
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-04-09 21:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-07 18:49 [Bug 48424] New: Fix warnings/errors reported by clang's scan-build tool bugzilla-daemon
2012-04-07 13:19 ` [Bug 48424] " bugzilla-daemon
2012-04-07 19:55 ` bugzilla-daemon
2012-04-09 14:30 ` bugzilla-daemon [this message]
2012-04-10 15:45 ` bugzilla-daemon
2012-04-14 17:37 ` bugzilla-daemon
2018-04-12 13:09 ` 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-48424-502-YLAYdZNb3F@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