ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Johannes Berg <johannes@sipsolutions.net>,
	Wolfram Sang <wsa@the-dreams.de>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] coverity, static checking etc.
Date: Wed, 14 May 2014 06:51:12 -0700	[thread overview]
Message-ID: <537374D0.8020307@roeck-us.net> (raw)
In-Reply-To: <1400074363.4759.8.camel@jlt4.sipsolutions.net>

On 05/14/2014 06:32 AM, Johannes Berg wrote:
> On Mon, 2014-05-12 at 11:32 +0200, Wolfram Sang wrote:
>>> is sent. Why not just tell them run this in-kernel tool with all
>>> that checking enabled before you send the patch?
>>
>> make C=1 ? That could be perhaps updated to call sparse *and* smatch if
>> it finds them installed.
>
> I do that with a simple wrapper:
>
> ~/bin/sparse:
> #!/bin/sh
>
> /path/to/real/sparse "$@" || exit 100
> /path/to/smatch -p=kernel "$@" || exit 200
>

I use "make C=1 ..." for sparse, followed by
"make C=1 CHECK="${SMATCH_PATH}/smatch --project=kernel ..."
for smatch.

Guenter

  reply	other threads:[~2014-05-14 13:51 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09 17:07 Dave Jones
2014-05-09 17:19 ` josh
2014-05-09 17:31   ` Johannes Berg
2014-05-09 17:54     ` Guenter Roeck
2014-05-09 18:04     ` Mark Brown
2014-05-09 19:08     ` Jiri Kosina
2014-05-09 19:41       ` Dmitry Torokhov
2014-05-09 19:29     ` Josh Triplett
2014-05-09 17:37 ` Bjorn Helgaas
2014-05-09 20:18 ` Arnd Bergmann
2014-05-09 20:33   ` Dave Jones
2014-05-09 21:39     ` Arnd Bergmann
2014-05-09 20:33 ` Roland Dreier
2014-05-09 20:52   ` Dave Jones
2014-05-09 20:57 ` tytso
2014-05-14 11:06   ` Dan Carpenter
2014-05-11 11:10 ` Wolfram Sang
2014-05-12  6:48   ` Michal Simek
2014-05-12  9:32     ` Wolfram Sang
2014-05-14 11:09       ` Dan Carpenter
2014-05-14 13:32       ` Johannes Berg
2014-05-14 13:51         ` Guenter Roeck [this message]
2014-05-14 15:22           ` Wolfram Sang
2014-05-14 15:44             ` Peter Huewe
2014-05-14 16:36               ` Wolfram Sang
2014-05-18 16:38     ` Mauro Carvalho Chehab
2014-05-19 10:13       ` Michal Simek
2014-05-12  8:58   ` Peter Senna Tschudin

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=537374D0.8020307@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=johannes@sipsolutions.net \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=wsa@the-dreams.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