From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@suse.com>
Cc: "backports@vger.kernel.org" <backports@vger.kernel.org>,
"cocci@systeme.lip6.fr" <cocci@systeme.lip6.fr>
Subject: Re: [PATCH 3/4] gentree.py: add SmPL patch equivalence proof support
Date: Mon, 08 Jun 2015 21:45:51 +0200 [thread overview]
Message-ID: <1433792751.10172.0.camel@sipsolutions.net> (raw)
In-Reply-To: <CAB=NE6X6=uuof0BdhVctobb_Ypvj-Q03Akma_PWGe17PUn=7PA@mail.gmail.com> (sfid-20150608_213135_744448_A746EA2B)
On Mon, 2015-06-08 at 12:31 -0700, Luis R. Rodriguez wrote:
> This is true, its in the like of how we wrote pycocci to provide us
> with a multithreaded solution for spatch integration / development as
> well and how pycocci now is upstream on Coccinelle.
Speaking of which - are you aware that pycocci fails (or rather doesn't
fail!) miserably when cocci isn't installed/in the $PATH? At least I got
a report to that extent, that it didn't really complete nor report an
error in that case.
johannes
next prev parent reply other threads:[~2015-06-08 19:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-06 0:09 [PATCH 0/4] backports: SmPL patch equivalence support Luis R. Rodriguez
2015-06-06 0:09 ` [PATCH 1/4] patches: remove bt_sock_stream_recvmsg() and bt_sock_recvmsg() from ifdefs Luis R. Rodriguez
2015-06-06 0:09 ` [PATCH 2/4] patches: change 0054-struct-proto_ops-sig backport strategy Luis R. Rodriguez
2015-06-06 0:10 ` [PATCH 3/4] gentree.py: add SmPL patch equivalence proof support Luis R. Rodriguez
2015-06-06 12:12 ` Johannes Berg
2015-06-08 19:31 ` Luis R. Rodriguez
2015-06-08 19:45 ` Johannes Berg [this message]
2015-06-08 20:08 ` Luis R. Rodriguez
2015-06-08 20:29 ` Johannes Berg
2015-06-06 0:10 ` [PATCH 4/4] patches: provide 0054-struct-proto_ops-sig SmPL patch replacement Luis R. Rodriguez
2015-06-06 5:33 ` [Cocci] " Julia Lawall
2015-06-08 21:00 ` Luis R. Rodriguez
2015-06-09 22:18 ` [PATCH 0/4] backports: SmPL patch equivalence support 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=1433792751.10172.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=backports@vger.kernel.org \
--cc=cocci@systeme.lip6.fr \
--cc=mcgrof@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