From: Dan Carpenter <error27@gmail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [0/4] inspector for sparse
Date: Fri, 23 Apr 2010 22:30:40 +0200 [thread overview]
Message-ID: <20100423203040.GL29093@bicker> (raw)
In-Reply-To: <w2j70318cbf1004021159y2fa50d58y62bd878c6355a972@mail.gmail.com>
On Fri, Apr 02, 2010 at 11:59:39AM -0700, Christopher Li wrote:
> I add a treeview branch on sparse/chrisl so you can pull from it.
>
> http://git.kernel.org/?p=devel/sparse/chrisl/sparse.git;a=shortlog;h=refs/heads/treeview
>
> In fedora, you need to install gtk2-devel package to enable it.
>
> Chris
This is an really useful program.
Inline functions don't show up in the list of functions. Is there a way
to inspect these as well? This is more a general sparse question, since
smatch doesn't parse inline functions either.
regards,
dan carpenter
next prev parent reply other threads:[~2010-04-23 20:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 18:36 [0/4] inspector for sparse Christopher Li
2010-04-02 18:59 ` Christopher Li
2010-04-23 20:30 ` Dan Carpenter [this message]
2010-04-23 20:37 ` Dan Carpenter
2010-04-25 8:37 ` Christopher Li
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=20100423203040.GL29093@bicker \
--to=error27@gmail.com \
--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).