linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Richard Palethorpe <rpalethorpe@suse.de>
Cc: linux-sparse@vger.kernel.org, pvorel@suze.cz, chrubis@suse.cz,
	io@richiejp.com
Subject: Re: Linux Test Project vendored Sparse
Date: Sun, 22 May 2022 14:22:27 +0200	[thread overview]
Message-ID: <20220522122227.mcgnatle6zmgqycn@mail> (raw)
In-Reply-To: <87k0ggbjb0.fsf@suse.de>

On Tue, Dec 07, 2021 at 01:33:56PM +0000, Richard Palethorpe wrote:
> Hello Sparse contributors,

Hi,

Please accept my apologies for replying so lately.
 
> After trying a number of static analysis tools we settled on Sparse to
> roll our own C checks.

Nice!

> We use a mixture of the linearized form and AST. If you are interested
> please see:
> https://github.com/linux-test-project/ltp/blob/master/tools/sparse/
> Also I will attach the main code to the body of this e-mail it is only
> 283 lines.
> 
> I still don't have a firm grasp on how Sparse works, so any feedback
> would be welcome. BTW we include Sparse as a git module and so far there
> have been no complaints.

I've taken a good look at it and everything look good.
I also think that using Sparse as a git module is the good choice.

If you have any question, do not hesitate to ask (I should be much
more responsive now).
 
Best regards,
-- Luc

  reply	other threads:[~2022-05-22 12:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07 13:33 Linux Test Project vendored Sparse Richard Palethorpe
2022-05-22 12:22 ` Luc Van Oostenryck [this message]
2022-05-23  6:45   ` Richard Palethorpe

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=20220522122227.mcgnatle6zmgqycn@mail \
    --to=luc.vanoostenryck@gmail.com \
    --cc=chrubis@suse.cz \
    --cc=io@richiejp.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=pvorel@suze.cz \
    --cc=rpalethorpe@suse.de \
    /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).