mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicolas Schier <nsc@kernel.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: "Nathan Chancellor" <nathan@kernel.org>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Shuah Khan" <skhan@linuxfoundation.org>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	"Luis Augenstein" <luis.augenstein@tngtech.com>,
	"Maximilian Huber" <maximilian.huber@tngtech.com>,
	"Pasha Tatashin" <pasha.tatashin@soleen.com>,
	"Pratyush Yadav" <pratyush@kernel.org>,
	"Alexander Graf" <graf@amazon.com>, "Willy Tarreau" <w@1wt.eu>,
	"Thomas Weißschuh" <linux@weissschuh.net>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Askar Safin" <safinaskar@gmail.com>,
	linux-doc@vger.kernel.org, kexec@lists.infradead.org,
	linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
	"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Subject: Re: [PATCH v3 0/2] Move tool for generating initramfs cpio to scripts/
Date: Sat, 26 Sep 2026 19:48:16 +0200	[thread overview]
Message-ID: <argFYF12qS0REcAP@levanger> (raw)
In-Reply-To: <areDq-1iFZUViDgS@kernel.org>

On Sat, Sep 26, 2026 at 11:34:51AM +0300, Mike Rapoport wrote:
> Hi Nicolas,
> 
> On Fri, Sep 25, 2026 at 09:29:29PM +0200, Nicolas Schier wrote:
> > initramfs cpio tools had been subject of several recent discussions on
> > linux-kbuild.  Let's get two minor steps forward by enabling a
> > top-level target for building gen_init_cpio w/o the need of a valid
> > kbuild configuration [1] and move the tools for generating the built-in
> > initramfs from usr/ to scripts/ [2].
> > 
> > Link: https://lore.kernel.org/all/20260220191150.244006-1-safinaskar@gmail.com # [1]
> > Link: https://lore.kernel.org/all/aSdrCFkUQup3qb-q@derry.ads.avm.de/ # [2]
> > ---
> > Changes in v3:
> >   * Update various remaining usr/gen_init* references treewide (Nathan)
> >   * Link to v2: https://patch.msgid.link/20260720-move-gen_init_cpio-to-scripts-v2-0-26b7e15c7133@kernel.org
> > 
> > Changes in v2:
> >   * Build gen_init_cpio only if CONFIG_BLK_DEV_INITRD (Thomas)
> >   * Keep underscore top-level target name (scripts_gen_init_cpio)
> >     (Thomas)
> >   * Link to v1: https://patch.msgid.link/20260309-move-gen_init_cpio-to-scripts-v1-0-0c5059b1ec5b@kernel.org
> > 
> > ---
> > Nicolas Schier (2):
> >       kbuild: Mark usr_gen_init_cpio as no-dot-config-target
> >       kbuild: Move gen_init_cpio and gen_initramfs.sh to scripts/
> > 
> >  .../early-userspace/early_userspace_support.rst          | 16 ++++++++--------
> >  Documentation/filesystems/ramfs-rootfs-initramfs.rst     | 10 +++++-----
> >  MAINTAINERS                                              |  1 +
> >  Makefile                                                 |  9 +++++----
> >  scripts/.gitignore                                       |  1 +
> >  scripts/Makefile                                         |  3 +++
> >  scripts/Makefile.package                                 |  2 +-
> >  {usr => scripts}/gen_init_cpio.c                         |  0
> >  {usr => scripts}/gen_initramfs.sh                        |  2 +-
> >  scripts/remove-stale-files                               |  2 ++
> >  scripts/sbom/tests/cmd_graph/test_savedcmd_parser.py     |  2 +-
> >  tools/testing/selftests/kho/vmtest.sh                    |  2 +-
> 
> There's also tools/testing/selftests/liveupdate/vmtest.sh I know of, didn't
> check for other users in tools/testing
> 

No idea how I missed that again; will be adjusted in v4.  Thanks a lot!

-- 
Nicolas

      reply	other threads:[~2026-09-26 17:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 19:29 Nicolas Schier
2026-09-25 19:29 ` [PATCH v3 1/2] kbuild: Mark usr_gen_init_cpio as no-dot-config-target Nicolas Schier
2026-09-25 19:33   ` sashiko-bot
2026-09-25 19:29 ` [PATCH v3 2/2] kbuild: Move gen_init_cpio and gen_initramfs.sh to scripts/ Nicolas Schier
2026-09-25 19:38   ` sashiko-bot
2026-09-26  8:34 ` [PATCH v3 0/2] Move tool for generating initramfs cpio " Mike Rapoport
2026-09-26 17:48   ` Nicolas Schier [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=argFYF12qS0REcAP@levanger \
    --to=nsc@kernel.org \
    --cc=corbet@lwn.net \
    --cc=graf@amazon.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux@weissschuh.net \
    --cc=luis.augenstein@tngtech.com \
    --cc=maximilian.huber@tngtech.com \
    --cc=nathan@kernel.org \
    --cc=pasha.tatashin@soleen.com \
    --cc=pratyush@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=rppt@kernel.org \
    --cc=safinaskar@gmail.com \
    --cc=skhan@linuxfoundation.org \
    --cc=thomas.weissschuh@linutronix.de \
    --cc=w@1wt.eu \
    /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®