From: SF Markus Elfring <elfring@users.sourceforge.net>
To: cocci@systeme.lip6.fr
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>,
Michal Marek <mmarek@suse.com>,
linux-kernel@vger.kernel.org
Subject: Re: scripts/coccinelle: require coccinelle >= 1.0.4 on device_node_continue.cocci
Date: Wed, 15 Jun 2016 18:06:32 +0200 [thread overview]
Message-ID: <ff2d8d68-20fb-1572-50e7-94a39107c442@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1606151753190.2887@hadrien>
> The above ocaml code just produces eg 1.0.5 or 1.0.5-dirty. I could drop
> the -dirty at the coccilib level, if that seems desirable.
Are there risks that any more fine-grained checks will be needed for
special functionality?
Regards,
Markus
next prev parent reply other threads:[~2016-06-15 16:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 22:10 [PATCH 0/4] scripts: add basic python version library and use it Luis R. Rodriguez
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 [this message]
2016-06-15 16:08 ` 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=ff2d8d68-20fb-1572-50e7-94a39107c442@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=cocci@systeme.lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mmarek@suse.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;
as well as URLs for NNTP newsgroup(s).