From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Julia.Lawall@lip6.fr, Gilles.Muller@lip6.fr,
nicolas.palix@imag.fr, mmarek@suse.com
Cc: linux-kernel@vger.kernel.org, cocci@systeme.lip6.fr,
"Luis R. Rodriguez" <mcgrof@kernel.org>
Subject: [PATCH 0/4] scripts: add basic python version library and use it
Date: Tue, 14 Jun 2016 15:10:13 -0700 [thread overview]
Message-ID: <1465942217-14452-1-git-send-email-mcgrof@kernel.org> (raw)
This series depends on the last set of coccicheck enhancements which
add parmap support and indexing heuristics.
Coccinelle SmPL files may often require advanced grammar techniques not
available in older versions of Coccinelle. We can use --parse-cocci and
bail if a file does not parse, however this doesn't tell us anything about
requirements. An alternative approach is to specifically do a check for
a version of coccinelle.
Since checking for versions can be generic we can just write a python
library to do these sorts of checks for us, this allows us to provide
a generic kernel library for version checks for any binary. This adds
that and then makes use of it as an example within a coccinelle SmPL
file which require a later version of coccinelle.
Luis R. Rodriguez (4):
coccicheck: propagate error and stop processing after first error
scripts: add reqs python library
coccicheck: enable use of the kernel's python library
scripts/coccinelle: require coccinelle >= 1.0.4 on
device_node_continue.cocci
MAINTAINERS | 1 +
scripts/coccicheck | 7 +
.../iterators/device_node_continue.cocci | 13 ++
scripts/lib/__init__.py | 1 +
scripts/lib/reqs.py | 211 +++++++++++++++++++++
5 files changed, 233 insertions(+)
create mode 100644 scripts/lib/__init__.py
create mode 100644 scripts/lib/reqs.py
--
2.8.2
next reply other threads:[~2016-06-14 22:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 22:10 Luis R. Rodriguez [this message]
2016-06-14 22:10 ` [PATCH 1/4] coccicheck: propagate error and stop processing after first error Luis R. Rodriguez
2016-06-14 22:10 ` [PATCH 2/4] scripts: add reqs python library Luis R. Rodriguez
2016-06-15 6:06 ` Julia Lawall
2016-06-15 16:04 ` Luis R. Rodriguez
2016-06-15 7:50 ` Michal Marek
2016-06-15 16:02 ` Luis R. Rodriguez
2016-06-15 19:11 ` Michal Marek
2016-06-15 20:26 ` Luis R. Rodriguez
2016-06-15 20:31 ` Julia Lawall
2016-06-15 12:01 ` Aw: [Cocci] " SF Markus Elfring
2016-06-15 15:51 ` Luis R. Rodriguez
2016-06-14 22:10 ` [PATCH 3/4] coccicheck: enable use of the kernel's " Luis R. Rodriguez
2016-06-15 7:51 ` Michal Marek
2016-06-15 15:43 ` Luis R. Rodriguez
2016-06-14 22:10 ` [PATCH 4/4] scripts/coccinelle: require coccinelle >= 1.0.4 on device_node_continue.cocci Luis R. Rodriguez
2016-06-15 6:08 ` Julia Lawall
2016-06-15 15:45 ` Luis R. Rodriguez
2016-06-15 8:43 ` Julia Lawall
2016-06-15 15:49 ` Luis R. Rodriguez
2016-06-15 15:55 ` Julia Lawall
2016-06-15 16:06 ` SF Markus Elfring
2016-06-15 16:08 ` [PATCH 4/4] " Luis R. Rodriguez
2016-06-15 16:11 ` Julia Lawall
2016-06-15 16:46 ` Luis R. Rodriguez
2016-06-15 16:52 ` Julia Lawall
2016-06-15 19:08 ` Luis R. Rodriguez
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=1465942217-14452-1-git-send-email-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=Gilles.Muller@lip6.fr \
--cc=Julia.Lawall@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=nicolas.palix@imag.fr \
/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).