From: Nicolas Schier <nsc@kernel.org>
To: Tj <tj.iam.tj@proton.me>
Cc: linux-kbuild@vger.kernel.org, Nathan Chancellor <nathan@kernel.org>
Subject: Re: [PATCH v2 0/2] Move tool for generating initramfs cpio to scripts/
Date: Tue, 4 Aug 2026 13:38:41 +0200 [thread overview]
Message-ID: <anHPQQp0Fjd3HPwj@levanger> (raw)
In-Reply-To: <anEE6Zy9DmNzOqDZ@mail.iam.tj>
On Mon, Aug 03, 2026 at 09:15:39PM +0000, Tj wrote:
> I've almost finished the feature to add to usr/gen_initramfs.sh::dir_filelist()
> parsing of:
>
> filter:/path/to/filter_script.sh:/path/to/directory/
>
> A generic solution that can generate a cpio list dynamically.
>
> My feature's current status is "working well".
>
> I use it to include a sub-set of just-built modules in the initramfs
> with some additional ./Makefile top-level magic.
>
> I noticed this proposal to move scripts so want to provide a heads-up.
>
> I described the technique as 'sneaky' in my email of 30th July:
>
> "How to move usr/Makefile call to just before vmlinux_a target ?"
>
> In it I add usr/Makefile.add_modules. It relies on being able to include,
> unmodified, usr/Makefile, and use its targets.
>
> Does moving usr/gen_initramfs.sh to scripts/ infer my 'example' script
>
> usr/gen_initramfs_dirlist_filter.sh
>
> should also be prepared to move to scripts/ ? It feels like that would
> be moving it from its logical home.
I think so, but guessing w/o concrete patches is probably not very
reliable.
> Due to the trial-and-error process whilst developing it, and much additional debug
> logging to understand call flows, it is not currently in a state to propose.
>
> My aim is to clean it up by end of this week (8th August) and post an
> RFC patch series.
Please go ahead. I will not able to have a in-depth look at it before
mid-August.
--
Nicolas
next prev parent reply other threads:[~2026-08-04 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 21:15 [PATCH v2 0/2] Move tool for generating initramfs cpio to scripts/ Tj
2026-08-04 11:38 ` Nicolas Schier [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-20 19:10 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=anHPQQp0Fjd3HPwj@levanger \
--to=nsc@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=tj.iam.tj@proton.me \
/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