From: Pavel Roskin <proski@gnu.org>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: Undetected error cases
Date: Sun, 01 Jun 2008 14:58:25 -0400 [thread overview]
Message-ID: <1212346705.2727.6.camel@dv> (raw)
In-Reply-To: <19f34abd0806011142x7e56fd8gf51358bf606ede91@mail.gmail.com>
On Sun, 2008-06-01 at 20:42 +0200, Vegard Nossum wrote:
> None of these produce errors or even warnings when they are run
> through sparse. I probably won't get around to fixing these myself
> since I'm not that familiar with sparse internals. This is just a
> heads up :-)
Still, you may be able to create test cases for the testsuite.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-06-01 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 18:42 Undetected error cases Vegard Nossum
2008-06-01 18:55 ` Vegard Nossum
2008-06-01 18:58 ` Pavel Roskin [this message]
2008-06-01 19:46 ` Vegard Nossum
2008-06-01 20:10 ` Pavel Roskin
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=1212346705.2727.6.camel@dv \
--to=proski@gnu.org \
--cc=linux-sparse@vger.kernel.org \
--cc=vegard.nossum@gmail.com \
/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).