From: Nathan Chancellor <nathan@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nicolas.schier@linux.dev>,
Nicolas Schier <nsc@kernel.org>
Cc: "Ahmad Fatoum" <a.fatoum@pengutronix.de>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Simon Glass" <sjg@chromium.org>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: Add top-level target for building gen_init_cpio
Date: Fri, 19 Dec 2025 14:58:56 -0700 [thread overview]
Message-ID: <176618153620.1413064.2360637802920518770.b4-ty@kernel.org> (raw)
In-Reply-To: <20251128-kbuild-add-top-level-target-for-building-gen_init_cpio-v1-1-84c63a8fc8d4@kernel.org>
On Fri, 28 Nov 2025 21:01:55 +0100, Nicolas Schier wrote:
> Add a top-level target for building gen_init_cpio to prevent re-entering
> kbuild for 'modules-cpio-pkg'.
>
> The recently introduced target 'modules-cpio-pkg' depends on
> gen_init_cpio but there is no simple way to add this dependency as a
> prerequisite that can be built in parallel to other recipes.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux.git kbuild-next
Thanks!
[1/1] kbuild: Add top-level target for building gen_init_cpio
https://git.kernel.org/kbuild/c/f8e05c10631e6
Please look out for regression or issue reports or other follow up
comments, as they may result in the patch/series getting dropped or
reverted.
Best regards,
--
Nathan Chancellor <nathan@kernel.org>
prev parent reply other threads:[~2025-12-19 21:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 20:01 [PATCH] kbuild: Add top-level target for building gen_init_cpio Nicolas Schier
2025-12-01 23:36 ` Nathan Chancellor
2025-12-19 21:58 ` Nathan Chancellor [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=176618153620.1413064.2360637802920518770.b4-ty@kernel.org \
--to=nathan@kernel.org \
--cc=a.fatoum@pengutronix.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.schier@linux.dev \
--cc=nsc@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sjg@chromium.org \
--cc=thomas.weissschuh@linutronix.de \
/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