From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: smatch warnings in current upstream kernel
Date: Tue, 11 Sep 2012 11:06:40 +0000 [thread overview]
Message-ID: <20120911110640.GB1244@localhost> (raw)
In-Reply-To: <20120911105127.GD19410@mwanda>
On Tue, Sep 11, 2012 at 01:51:27PM +0300, Dan Carpenter wrote:
> On Tue, Sep 11, 2012 at 06:10:02PM +0800, Fengguang Wu wrote:
> > Here are the 7161 smatch warnings for 2139 files in upstream head
> > 1a95620f45155ac523cd1419d89150fbb4eb858b. It's not a complete build
> > (no make clean), so does not include all possible warnings.
> >
>
> There are some sparse warnings mixed in as well. They would have
> been sent to stderr and smatch warnings get sent to stdout.
Thanks for pointing this out!
> But if you want you could look at smatch_scripts/test_kernel.sh
> which allows for a parallel build and saves all the warnings in
> warns.txt.
Yeah I looked at the script, however did not want to touch the source
tree, so...
> I guess you have your own parallel build technique as well and that
> works too.
I have a tiny smatch wrapper script for passing to CHECK=.
According to your advice, I will only save its stdout:
$SMATCH -p kernel "$@" > $SMATCH_OUT_ROOT/$PPID-$$-$RANDOM
Thanks,
Fengguang
next prev parent reply other threads:[~2012-09-11 11:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 10:51 smatch warnings in current upstream kernel Dan Carpenter
2012-09-11 11:06 ` Fengguang Wu [this message]
2012-09-11 14:29 ` Dan Carpenter
2012-09-11 14:49 ` Fengguang Wu
2012-09-12 2:48 ` Fengguang Wu
2012-09-12 6:26 ` 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=20120911110640.GB1244@localhost \
--to=fengguang.wu@intel.com \
--cc=kernel-janitors@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