From: Josh Triplett <josh@freedesktop.org>
To: Christopher Li <sparse@chrisli.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: How do I get the latest sparse?
Date: Tue, 16 Jan 2007 21:41:49 -0800 [thread overview]
Message-ID: <45ADB71D.3080502@freedesktop.org> (raw)
In-Reply-To: <20070117014923.GA641@chrisli.org>
[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]
Christopher Li wrote:
> On Tue, Jan 16, 2007 at 04:23:57AM -0800, Josh Triplett wrote:
>> I've followed all the patches on linux-sparse, and I have tested several of
>> them in local git; I just haven't pushed out new bits. I particularly look
>
> Great to know you are back. I can resend my stack of patches now :-)
In general, you only need to resend if you have changes. Otherwise, I can
just use the previous versions you mailed. :)
Currently working my way through your resent patches.
>> forward to integrating your NULL pointer checking code, and I think I can
>
> I haven't get much feed back of the new checking code yet.
Expect some comments in response to your new patch shortly.
> I will refresh my patch as well.
It probably still applied. :)
> Without cross function/file checking, the interrupt checking generates way
> too many false positives.
Sounds a lot like the context checking. :)
The use of strcmp on asm strings for x86 instruction mnemonics seems like a
problem, though.
> I am working on the cross file checking right now.
Excellent. I would welcome any attempts at cross-function and cross-file
checking, rather than continuing to add annotations for that purpose.
- Josh Triplett
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2007-01-17 5:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 23:48 How do I get the latest sparse? Mitesh Shah
2007-01-16 0:17 ` Christopher Li
2007-01-16 12:23 ` Josh Triplett
2007-01-17 1:49 ` Christopher Li
2007-01-17 5:41 ` Josh Triplett [this message]
2007-01-17 6:31 ` Christopher Li
2007-01-17 19:05 ` Sam Ravnborg
2007-01-17 20:03 ` Christopher Li
2007-01-16 0:59 ` Randy Dunlap
2007-01-16 1:07 ` Mitesh Shah
2007-01-16 2:15 ` Randy Dunlap
2007-01-16 3:16 ` Dave Jones
2007-01-16 12:14 ` Josh Triplett
2007-01-16 15:40 ` Mitesh Shah
2007-01-17 0:23 ` Dave Jones
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=45ADB71D.3080502@freedesktop.org \
--to=josh@freedesktop.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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).