public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Bastian Germann <bage@linutronix.de>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/1] kbuild: deb-pkg: Build parallely with current dpkg-buildpackage
Date: Tue, 21 Mar 2023 11:28:54 +0100	[thread overview]
Message-ID: <4be55ba4-d3fa-dfa9-7b38-13f3ced20ad2@linutronix.de> (raw)
In-Reply-To: <CAK7LNASckF_6QLHkvLEk3b8nE23v4Qy4wmm4FHd5BrDo6U2x2g@mail.gmail.com>

Am 21.03.23 um 11:18 schrieb Masahiro Yamada:
> "make bindeb-pkg" also runs in 16 threads because
> $(DEB_BUILD_OPTIONS) always contains "parallel=16"
> even if -j<N> option is given at all.
> 
> In other words, this patch will take away user's freedom
> to choose the number of threads.

Okay. To solve this, I would forward make's -j option to the dpkg-buildpackage calls,
which is now called with the defaults.

I think you should see the warning with older dpkg-buildpackage versions without the
patch applied as well because their default is dpkg-buildpackage -j`nproc` and is in
effect currently.

  reply	other threads:[~2023-03-21 10:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 17:35 [PATCH v3 0/1] kbuild: deb-pkg: Build parallely with current dpkg-buildpackage Bastian Germann
2023-03-15 17:35 ` [PATCH v3 1/1] " Bastian Germann
2023-03-21 10:18   ` Masahiro Yamada
2023-03-21 10:28     ` Bastian Germann [this message]
2023-04-10 12:26       ` Masahiro Yamada

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=4be55ba4-d3fa-dfa9-7b38-13f3ced20ad2@linutronix.de \
    --to=bage@linutronix.de \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.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