From: Knut Omang <knut.omang@oracle.com>
To: linux-kernel@vger.kernel.org
Cc: "Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Nicolas Palix" <nicolas.palix@imag.fr>,
"Masahiro Yamada" <yamada.masahiro@socionext.com>,
linux-kbuild@vger.kernel.org,
"Håkon Bugge" <haakon.bugge@oracle.com>,
linux-doc@vger.kernel.org, "Jonathan Corbet" <corbet@lwn.net>,
"Gilles Muller" <Gilles.Muller@lip6.fr>,
"Tom Saeger" <tom.saeger@oracle.com>,
"Michal Marek" <michal.lkml@markovi.net>,
"Mickaël Salaün" <mic@digikod.net>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
"Julia Lawall" <Julia.Lawall@lip6.fr>,
"John Haxby" <john.haxby@oracle.com>,
"Åsmund Østvold" <asmund.ostvold@oracle.com>,
"Matthew Wilcox" <willy@infradead.org>,
"Levin, Alexander (Sasha Levin)" <alexander.levin@verizon.com>,
cocci@systeme.lip6.fr,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [PATCH v4 1/1] runchecks: Generalize make C={1,2} to support multiple checkers
Date: Mon, 05 Feb 2018 07:41:39 +0100 [thread overview]
Message-ID: <1517812899.3118.372.camel@oracle.com> (raw)
In-Reply-To: <c271ba8f99393585d69db71f40db3c01c44769e4.1516356501.git-series.knut.omang@oracle.com>
On Fri, 2018-01-19 at 11:14 +0100, Knut Omang wrote:
> Add scripts/runchecks which has generic support for running
> checker tools in a convenient and user friendly way that
> the author hopes can contribute to rein in issues detected
> by these tools in a manageable and convenient way.
>
> scripts/runchecks provides the following basic functionality:
>
> * Makes it possible to selectively suppress output from individual
> checks on a per file or per subsystem basis.
> * Unifies output and suppression input from different tools
> by providing a single unified syntax and presentation for the
> underlying tools in the style of "scripts/checkpatch.pl --show-types".
> * Allows selective run of one, or more (or all) configured tools
> for each file.
>
> In the Makefile system, the sparse specific setup has been replaced
> by setup for runchecks.
Hi all,
- Anything more I can/need to do to bring this forward?
- Any quiet concerns?
I realize it is a subsystem crossing change, and a lot going on elsewhere,
nevertheless I believe this is a time saver in the slightly longer run,
as it allows automation of checking, even without a "perfect"
code base to begin with.
Thanks,
Knut
next prev parent reply other threads:[~2018-02-05 6:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 10:14 [PATCH v4 0/1] Support for generalized use of make C={1,2} via a wrapper program Knut Omang
2018-01-19 10:14 ` [PATCH v4 1/1] runchecks: Generalize make C={1,2} to support multiple checkers Knut Omang
2018-02-05 6:41 ` Knut Omang [this message]
2018-02-05 7:03 ` Masahiro Yamada
2018-02-05 7:20 ` Knut Omang
2018-03-20 5:44 ` Knut Omang
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=1517812899.3118.372.camel@oracle.com \
--to=knut.omang@oracle.com \
--cc=Gilles.Muller@lip6.fr \
--cc=Julia.Lawall@lip6.fr \
--cc=akpm@linux-foundation.org \
--cc=alexander.levin@verizon.com \
--cc=asmund.ostvold@oracle.com \
--cc=cocci@systeme.lip6.fr \
--cc=corbet@lwn.net \
--cc=haakon.bugge@oracle.com \
--cc=john.haxby@oracle.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mic@digikod.net \
--cc=michal.lkml@markovi.net \
--cc=nicolas.palix@imag.fr \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tom.saeger@oracle.com \
--cc=willy@infradead.org \
--cc=yamada.masahiro@socionext.com \
/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