From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Julia.Lawall@lip6.fr, nicolas.palix@imag.fr,
Gilles.Muller@lip6.fr, mmarek@suse.com
Cc: akpm@linux-foundation.org, gregkh@linuxfoundation.org,
markivx@codeaurora.org, stephen.boyd@linaro.org,
zohar@linux.vnet.ibm.com, broonie@kernel.org,
ming.lei@canonical.com, tiwai@suse.d, johannes@sipsolutions.net,
chunkeey@googlemail.com, hauke@hauke-m.de,
jwboyer@fedoraproject.org, dmitry.torokhov@gmail.com,
dwmw2@infradead.org, jslaby@suse.com,
torvalds@linux-foundation.org, deepa.kernel@gmail.com,
keescook@chromium.org, cocci@systeme.lip6.fr,
linux-kernel@vger.kernel.org,
"Luis R. Rodriguez" <mcgrof@kernel.org>
Subject: [PATCH v4 0/9] coccicheck: modernize
Date: Wed, 29 Jun 2016 15:14:50 -0700 [thread overview]
Message-ID: <1467238499-10889-1-git-send-email-mcgrof@kernel.org> (raw)
There were quite a bit of comments from the v3 series [0], since there
was quite a bit of review needed for some other changes I've had discussions
with Nicolas and Julia privately over these changes and collected their Acks
privately to avoid unnecessary e-mail waste. I've annotated the changes
in the commit log with any changes done in the v4 series. If most importance
is the use of .cocciconfig, update of the documentation and recommending an
upgrade of coccinelle for users wishing to use idutils. A future 1.0.6 release
of coccinellew will support it best.
This series is rebased on top of linux-next tag next-20160629, I've put
up a branch of these changes up on my linux-next tree, the branch is
20160629-coccicheck-v4 [1].
[0] https://lkml.kernel.org/r/1466536893-23355-1-git-send-email-mcgrof@kernel.org
[1] https://git.kernel.org/cgit/linux/kernel/git/mcgrof/linux-next.git/log/?h=20160629-coccicheck-v4
Luis R. Rodriguez (9):
coccicheck: move spatch binary check up
coccicheck: make SPFLAGS more useful
coccicheck: enable parmap support
coccicheck: add support for DEBUG_FILE
coccicheck: replace --very-quiet with --quiet when debugging
scripts: add Linux .cocciconfig for coccinelle
coccicheck: add support for requring a coccinelle version
coccicheck: refer to Documentation/coccinelle.txt and wiki
scripts/coccinelle: require coccinelle >= 1.0.4 on
device_node_continue.cocci
.cocciconfig | 3 +
.gitignore | 1 +
Documentation/coccinelle.txt | 148 ++++++++++++++++++++-
scripts/coccicheck | 94 +++++++++++--
.../iterators/device_node_continue.cocci | 3 +
5 files changed, 239 insertions(+), 10 deletions(-)
create mode 100644 .cocciconfig
--
2.8.4
next reply other threads:[~2016-06-29 22:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 22:14 Luis R. Rodriguez [this message]
2016-06-29 22:14 ` [PATCH v4 1/9] coccicheck: move spatch binary check up Luis R. Rodriguez
2016-06-29 22:14 ` [PATCH v4 2/9] coccicheck: make SPFLAGS more useful Luis R. Rodriguez
2016-06-29 22:14 ` [PATCH v4 3/9] coccicheck: enable parmap support Luis R. Rodriguez
2016-06-29 22:14 ` [PATCH v4 4/9] coccicheck: add support for DEBUG_FILE Luis R. Rodriguez
2016-06-29 22:14 ` [PATCH v4 5/9] coccicheck: replace --very-quiet with --quiet when debugging Luis R. Rodriguez
2016-06-29 22:14 ` [PATCH v4 6/9] scripts: add Linux .cocciconfig for coccinelle Luis R. Rodriguez
2016-06-29 22:14 ` [PATCH v4 7/9] coccicheck: add support for requring a coccinelle version Luis R. Rodriguez
2016-06-29 22:14 ` [PATCH v4 8/9] coccicheck: refer to Documentation/coccinelle.txt and wiki Luis R. Rodriguez
2016-06-29 22:14 ` [PATCH v4 9/9] scripts/coccinelle: require coccinelle >= 1.0.4 on device_node_continue.cocci Luis R. Rodriguez
2016-07-13 21:45 ` [PATCH v4 0/9] coccicheck: modernize Luis R. Rodriguez
2016-07-22 10:14 ` Michal Marek
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=1467238499-10889-1-git-send-email-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=Gilles.Muller@lip6.fr \
--cc=Julia.Lawall@lip6.fr \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=chunkeey@googlemail.com \
--cc=cocci@systeme.lip6.fr \
--cc=deepa.kernel@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=hauke@hauke-m.de \
--cc=johannes@sipsolutions.net \
--cc=jslaby@suse.com \
--cc=jwboyer@fedoraproject.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markivx@codeaurora.org \
--cc=ming.lei@canonical.com \
--cc=mmarek@suse.com \
--cc=nicolas.palix@imag.fr \
--cc=stephen.boyd@linaro.org \
--cc=tiwai@suse.d \
--cc=torvalds@linux-foundation.org \
--cc=zohar@linux.vnet.ibm.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