From: Ian Campbell <ijc@hellion.org.uk>
To: Greg Dietsche <Gregory.Dietsche@cuw.edu>
Cc: julia@diku.dk, Gilles.Muller@lip6.fr, npalix.work@gmail.com,
rdunlap@xenotime.net, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, cocci@diku.dk
Subject: Re: [PATCH 0/3] coccinelle: add parallel execution
Date: Thu, 14 Jul 2011 10:37:19 +0100 [thread overview]
Message-ID: <1310636239.634.493.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <1310520405-1558-1-git-send-email-Gregory.Dietsche@cuw.edu>
On Tue, 2011-07-12 at 20:26 -0500, Greg Dietsche wrote:
> This patch series adds a new flag PARALLEL= to the coccicheck build target and documents the new feature.
> It works a lot like make's -j flag. I looked for a way to have make pass on the value of -j, but
> didn't find one - if anyone knows how to do that, I'd love to hear about it!
I suppose in principal you could parse $MAKEFLAGS (or $MFLAGS) for
--jobserver-fds and implement compatibility with make's jobserver
protocol ( http://mad-scientist.net/make/jobserver.html ). I don't know
stable or outward facing the make guys consider that interface, plus it
all sounds a bit fiddly to me...
Ian.
--
Ian Campbell
QOTD:
"I thought I saw a unicorn on the way over, but it was just a
horse with one of the horns broken off."
prev parent reply other threads:[~2011-07-14 9:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 1:26 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
2011-07-26 22:36 ` [PATCH v2] " Greg Dietsche
2011-07-27 6:18 ` Nicolas Palix
2011-07-14 9:37 ` Ian Campbell [this message]
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=1310636239.634.493.camel@zakaz.uk.xensource.com \
--to=ijc@hellion.org.uk \
--cc=Gilles.Muller@lip6.fr \
--cc=Gregory.Dietsche@cuw.edu \
--cc=cocci@diku.dk \
--cc=julia@diku.dk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npalix.work@gmail.com \
--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
all inboxes | Powered by JetHome®