From: Dan Carpenter <dan.carpenter@oracle.com>
To: Sami Kerola <kerolasa@iki.fi>
Cc: Karel Zak <kzak@redhat.com>,
util-linux <util-linux@vger.kernel.org>,
linux-sparse@vger.kernel.org
Subject: Re: [PATCH 0/7] pull: make smatch scan output easy to digest
Date: Sat, 25 Feb 2017 23:09:13 +0300 [thread overview]
Message-ID: <20170225195901.GB4570@mwanda> (raw)
In-Reply-To: <alpine.LNX.2.20.1702251653080.16457@imuri>
On Sat, Feb 25, 2017 at 05:32:23PM +0000, Sami Kerola wrote:
> See below simple source file that demonstrates how to triggers warning in
> question. When I said was 'smatch' printed warnings it was cgcc that was
> complaining , and therefore this is not really a 'smatch' problem at all.
> Sorry about giving wrong impression.
cgcc is just a shell script which calls either smatch or sparse. Smatch
uses sparse as a parser so you sometimes do see certain sparse messages
when you run smatch, but I don't do bug fixes for those normally. You
would think I would understand sparse really well because I use it so
much but actually hacking sparse makes me realize I'm kind of dumb. ;P
regards,
dan carpenter
next prev parent reply other threads:[~2017-02-25 20:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 22:06 [PATCH 0/7] pull: make smatch scan output easy to digest Sami Kerola
2017-02-13 22:06 ` [PATCH 1/7] cfdisk: avoid use of VLA in combination with sizeof() [smatch scan] Sami Kerola
2017-02-13 22:06 ` Sami Kerola
2017-02-13 22:06 ` [PATCH 3/7] misc: add static keyword to where needed " Sami Kerola
2017-02-13 22:06 ` [PATCH 4/7] misc: unify function declarations " Sami Kerola
2017-02-13 22:06 ` [PATCH 5/7] lib/idcache: add void to function declaration " Sami Kerola
2017-02-13 22:06 ` [PATCH 6/7] libblkid: declare across file variables in blkidP.h " Sami Kerola
2017-02-13 22:06 ` [PATCH 7/7] findmnt: fix couple memory leaks [cppcheck] Sami Kerola
2017-02-20 12:14 ` [PATCH 0/7] pull: make smatch scan output easy to digest Karel Zak
2017-02-20 22:12 ` Sami Kerola
2017-02-21 9:50 ` Karel Zak
2017-02-24 0:37 ` Dan Carpenter
2017-02-25 17:32 ` Sami Kerola
2017-02-25 20:09 ` Dan Carpenter [this message]
2017-02-26 4:07 ` Luc Van Oostenryck
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=20170225195901.GB4570@mwanda \
--to=dan.carpenter@oracle.com \
--cc=kerolasa@iki.fi \
--cc=kzak@redhat.com \
--cc=linux-sparse@vger.kernel.org \
--cc=util-linux@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