Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/7] automatically determine job concurrency
Date: Sun, 24 Jun 2012 11:13:52 +0200	[thread overview]
Message-ID: <87obo99inj.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1339466983-19786-1-git-send-email-ntl@pobox.com> (Nathan Lynch's message of "Mon, 11 Jun 2012 21:09:36 -0500")

>>>>> "Nathan" == Nathan Lynch <ntl@pobox.com> writes:

 Nathan> This series implements the option of "autodetecting" the number of
 Nathan> jobs to run concurrently (make -jN), using the number of reported CPUs
 Nathan> when BR2_JLEVEL is set to 0.

Committed series, thanks!

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2012-06-24  9:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12  2:09 [Buildroot] [PATCH 0/7] automatically determine job concurrency Nathan Lynch
2012-06-12  2:09 ` [Buildroot] [PATCH 1/7] introduce PARALLEL_JOBS build system variable Nathan Lynch
2012-06-12  2:09 ` [Buildroot] [PATCH 2/7] boost: change uses of BR2_JLEVEL to PARALLEL_JOBS Nathan Lynch
2012-06-12  2:09 ` [Buildroot] [PATCH 3/7] cmake: change use " Nathan Lynch
2012-06-12  2:09 ` [Buildroot] [PATCH 4/7] midori: " Nathan Lynch
2012-06-12  2:09 ` [Buildroot] [PATCH 5/7] qt: " Nathan Lynch
2012-06-12  2:09 ` [Buildroot] [PATCH 6/7] toolchain/crosstool-ng: " Nathan Lynch
2012-06-12  2:09 ` [Buildroot] [PATCH 7/7] automatically set PARALLEL_JOBS when BR2_JLEVEL is 0 Nathan Lynch
2012-06-13 23:27   ` Arnout Vandecappelle
2012-06-13 23:44     ` Nathan Lynch
2012-06-14  6:07       ` Peter Korsgaard
2012-06-14  6:16         ` Nathan Lynch
2012-06-14  8:56           ` Peter Korsgaard
2012-06-14  8:33     ` Richard Braun
2012-06-14 15:02   ` [Buildroot] [PATCHv2 " Nathan Lynch
2012-06-14 18:09     ` Baruch Siach
2012-06-16 19:37   ` [Buildroot] [PATCHv3 " Nathan Lynch
2012-06-24  9:13 ` Peter Korsgaard [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=87obo99inj.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.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