From: Sam Ravnborg <sam@ravnborg.org>
To: Dan Carpenter <error27@gmail.com>
Cc: smatch-discuss@lists.sf.net, linux-sparse@vger.kernel.org
Subject: Re: Moving smatch to use sparse
Date: Thu, 5 Oct 2006 11:26:56 +0200 [thread overview]
Message-ID: <20061005092656.GA17866@uranus.ravnborg.org> (raw)
In-Reply-To: <a63d67fe0610050141x251253fei59b93fff28505dc4@mail.gmail.com>
On Thu, Oct 05, 2006 at 01:41:03AM -0700, Dan Carpenter wrote:
> Work on smatch is going ahead. I have one real life check is working
> and I've added a patched up the core code quite a bit.
For the mindless - can you please repeat what smatch does?
Sam
next prev parent reply other threads:[~2006-10-05 9:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a63d67fe0607140925h3665cd98ibc2fab07f6f80360@mail.gmail.com>
2006-07-16 0:42 ` Moving smatch to use sparse Dan Carpenter
2006-10-05 8:41 ` Dan Carpenter
2006-10-05 9:26 ` Sam Ravnborg [this message]
2006-10-05 9:49 ` Dan Carpenter
2006-10-05 10:25 ` Jörn Engel
2006-10-06 6:31 ` Dan Carpenter
2006-10-05 15:52 ` Michael Stefaniuc
2006-10-05 20:58 ` Dan Carpenter
2006-10-05 22:46 ` Michael Stefaniuc
2006-10-06 8:57 ` Dan Carpenter
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=20061005092656.GA17866@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=error27@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=smatch-discuss@lists.sf.net \
/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).