From: Nicolas Schier <nsc@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>, Nicolas Schier <nsc@kernel.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Askar Safin <safinaskar@gmail.com>
Subject: [PATCH v2 1/2] kbuild: Mark usr_gen_init_cpio as no-dot-config-target
Date: Mon, 20 Jul 2026 21:10:31 +0200 [thread overview]
Message-ID: <20260720-move-gen_init_cpio-to-scripts-v2-1-26b7e15c7133@kernel.org> (raw)
In-Reply-To: <20260720-move-gen_init_cpio-to-scripts-v2-0-26b7e15c7133@kernel.org>
Let usr/gen_init_cpio be built also if there is no kernel configuration.
Askar Safin reported that gen_init_cpio may be of use before any kernel
configuration is available. Add usr_gen_init_cpio to list of targets
that do not require a .config file.
Reported-by: Askar Safin <safinaskar@gmail.com>
Closes: https://lore.kernel.org/all/20260220191150.244006-1-safinaskar@gmail.com
Fixes: f8e05c10631e ("kbuild: Add top-level target for building gen_init_cpio")
Signed-off-by: Nicolas Schier <nsc@kernel.org>
---
Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/Makefile b/Makefile
index b9c5792c79e0160b3c787f8a686bd60d9f8066d7..41f6a1917866119c472a8876134824aded20a616 100644
--- a/Makefile
+++ b/Makefile
@@ -298,6 +298,7 @@ no-dot-config-targets := $(clean-targets) \
%asm-generic kernelversion %src-pkg dt_binding_check \
dt_style_selftest \
outputmakefile rustavailable rustfmt rustfmtcheck \
+ usr_gen_init_cpio \
run-command
no-sync-config-targets := $(no-dot-config-targets) %install modules_sign kernelrelease \
image_name
--
2.47.3
next prev parent reply other threads:[~2026-07-20 19:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 19:10 [PATCH v2 0/2] Move tool for generating initramfs cpio to scripts/ Nicolas Schier
2026-07-20 19:10 ` Nicolas Schier [this message]
2026-07-20 19:10 ` [PATCH v2 2/2] kbuild: Move gen_init_cpio and gen_initramfs.sh " Nicolas Schier
2026-07-31 19:36 ` Nathan Chancellor
2026-08-01 19:44 ` Nicolas Schier
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=20260720-move-gen_init_cpio-to-scripts-v2-1-26b7e15c7133@kernel.org \
--to=nsc@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=safinaskar@gmail.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
all inboxes | Powered by JetHome®