From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Joe Perches <joe@perches.com>,
linux-kernel@vger.kernel.org, smatch@vger.kernel.org
Subject: Re: Smatch v1.56 released
Date: Wed, 07 Mar 2012 18:47:41 +0200 [thread overview]
Message-ID: <1331138861.3463.22.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20120305072220.GL22598@mwanda>
On Mon, 2012-03-05 at 10:22 +0300, Dan Carpenter wrote:
> What I do is only look at new bugs. I've got a script
> smatch_scripts/new_bugs.sh
> That takes the output from two smatch runs and prints the bugs which
> are new.
>
> Artem has a set of scripts he's working on as well.
Yeah, I basically compile with W=1, run
sparse/coccinelle/cppcheck/smatch before and after a patch, compare the
build logs and report about only new warnings. Quite useful when you are
a maintainer.
--
Best Regards,
Artem Bityutskiy
prev parent reply other threads:[~2012-03-07 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 18:04 Smatch v1.56 released Dan Carpenter
2012-03-04 18:38 ` Joe Perches
2012-03-04 19:08 ` Jiri Slaby
2012-03-05 7:22 ` Dan Carpenter
2012-03-07 16:47 ` Artem Bityutskiy [this message]
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=1331138861.3463.22.camel@sauron.fi.intel.com \
--to=artem.bityutskiy@linux.intel.com \
--cc=dan.carpenter@oracle.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=smatch@vger.kernel.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