From: Greg Dietsche <greg@gregd.org>
To: Michal Marek <mmarek@suse.cz>
Cc: Nicolas Palix <Nicolas.Palix@inria.fr>,
Greg Dietsche <gregory.dietsche@cuw.edu>,
Joe Perches <joe@perches.com>,
julia@diku.dk, Gilles.Muller@lip6.fr, rdunlap@xenotime.net,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
cocci@diku.dk
Subject: Re: [PATCH 3/3] coccicheck: add parallel execution
Date: Tue, 26 Jul 2011 17:46:32 -0500 [thread overview]
Message-ID: <4E2F43C8.8080805@gregd.org> (raw)
In-Reply-To: <4E2EC6C7.3080009@suse.cz>
On 7/26/2011 8:53 AM, Michal Marek wrote:
> Why not move the loop into some Makefile and let make take care of the
> parallel execution? Something among the lines of
>
> results := check1.out check2.out ... (generated)
> coccicheck: $(results)
> cat $^
>
> %.out: FORCE
> ... run given test and store its result ...
>
> then the user can simply type make -j6 coccicheck.
>
> Note: I haven't seen the patch, I only got Nicolas' mail now.
>
> Michal
>
yes, I agree, that would be better - especially from a user perspective.
I'm not much of a makefile expert at all. I did try that approach
initially, but it seemed like it was going to turn into a rewrite of the
coccinelle script. If someone can do it via make, I'd say go for it :)
I won't have much free time for the foreseeable future to tackle it.
using "make -j" is much more comfortable and intuitive than typing
PARALLEL= ...
Greg
next prev parent reply other threads:[~2011-07-26 22:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 1:26 [PATCH 0/3] coccinelle: add parallel execution Greg Dietsche
2011-07-13 1:26 ` [PATCH 1/3] coccinelle.txt: add overview section Greg Dietsche
2011-07-26 14:46 ` Nicolas Palix
2011-07-13 1:26 ` [PATCH 2/3] coccinelle.txt: add documentation of PARALLEL= flag Greg Dietsche
2011-07-27 6:19 ` Nicolas Palix
2011-07-13 1:26 ` [PATCH 3/3] coccicheck: add parallel execution Greg Dietsche
2011-07-13 2:42 ` Joe Perches
2011-07-14 2:14 ` Greg Dietsche
2011-07-26 13:33 ` Nicolas Palix
2011-07-26 13:53 ` Michal Marek
2011-07-26 22:46 ` Greg Dietsche [this message]
2011-07-26 22:36 ` [PATCH v2] " Greg Dietsche
2011-07-27 6:18 ` Nicolas Palix
2011-07-14 9:37 ` [PATCH 0/3] coccinelle: " Ian Campbell
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=4E2F43C8.8080805@gregd.org \
--to=greg@gregd.org \
--cc=Gilles.Muller@lip6.fr \
--cc=Nicolas.Palix@inria.fr \
--cc=cocci@diku.dk \
--cc=gregory.dietsche@cuw.edu \
--cc=joe@perches.com \
--cc=julia@diku.dk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=rdunlap@xenotime.net \
/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