mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Askar Safin <safinaskar@gmail.com>
To: nsc@kernel.org
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	nathan@kernel.org, safinaskar@gmail.com,
	Rob Landley <rob@landley.net>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 0/2] Move tool for generating initramfs cpio to scripts/
Date: Tue, 10 Mar 2026 04:54:16 +0300	[thread overview]
Message-ID: <20260310015416.3034078-1-safinaskar@gmail.com> (raw)
In-Reply-To: <20260309-move-gen_init_cpio-to-scripts-v1-0-0c5059b1ec5b@kernel.org>

I like this patchset.

Rob (CC'd), does this solve your problem?

Also, in [1] I said:
> command
> "make usr/gen_init_cpio" doesn't work in clean kernel tree even if
> config exists (I checked this)

Now I tested this again, and I see that "make usr/gen_init_cpio" indeed
doesn't work in current mainline in that scenario, but
"cd usr; make gen_init_cpio" works (how I supposed to know this?).
So, problems in [1] are not as big as I thought. You don't need to build
whole kernel two times in that scenario. But still I like this your
new patchset.

Also, I think that top-level "usr" directory exists as a placeholder for
klibc-init project (this is merely my hypothesis, I don't know for sure).
I. e. it was supposed to contain source for userspace init program, which
was supposed to be put into default initramfs.

But klibc-init project, unfortunately, seems to fail. So, I think we should
remove whole top level "usr" directory and move its contents to other places.

[1] https://lore.kernel.org/all/20260220191150.244006-1-safinaskar@gmail.com



-- 
Askar Safin

  parent reply	other threads:[~2026-03-10  1:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09  7:56 Nicolas Schier
2026-03-09  7:56 ` [PATCH 1/2] kbuild: Mark usr_gen_init_cpio as no-dot-config-target Nicolas Schier
2026-03-09  7:56 ` [PATCH 2/2] kbuild: Move gen_init_cpio and gen_initramfs.sh to scripts/ Nicolas Schier
2026-03-09 13:41   ` Thomas Weißschuh
2026-03-10  7:14     ` Nicolas Schier
2026-03-10  9:13       ` Thomas Weißschuh
2026-03-12 13:59         ` Nicolas Schier
2026-03-10  1:49   ` Askar Safin
2026-03-10  6:24     ` Nicolas Schier
2026-03-22 12:50       ` Askar Safin
2026-03-10  1:54 ` Askar Safin [this message]
2026-03-10  4:30   ` [PATCH 0/2] Move tool for generating initramfs cpio " H. Peter Anvin

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=20260310015416.3034078-1-safinaskar@gmail.com \
    --to=safinaskar@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=nsc@kernel.org \
    --cc=rob@landley.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®