From: Martin Wilck <mwilck@suse.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Andrew Morton <akpm@linux-foundation.org>,
David Disseldorp <ddiss@suse.de>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>
Cc: Askar Safin <safinaskar@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] init: INITRAMFS_PRESERVE_MTIME should depend on BLK_DEV_INITRD
Date: Mon, 15 Sep 2025 13:39:38 +0200 [thread overview]
Message-ID: <aa5d1e137ddab12d1fa6beca4279fd9c90ff58dd.camel@suse.com> (raw)
In-Reply-To: <9a65128514408dc7de64cf4fea75c1a8342263ea.1757920006.git.geert+renesas@glider.be>
On Mon, 2025-09-15 at 09:11 +0200, Geert Uytterhoeven wrote:
> INITRAMFS_PRESERVE_MTIME is only used in init/initramfs.c and
> init/initramfs_test.c. Hence add a dependency on BLK_DEV_INITRD, to
> prevent asking the user about this feature when configuring a kernel
> without initramfs support.
>
> Fixes: 1274aea127b2e8c9 ("initramfs: add INITRAMFS_PRESERVE_MTIME
> Kconfig option")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Reviewed-by: Martin Wilck <mwilck@suse.com>
> ---
> init/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/init/Kconfig b/init/Kconfig
> index e3eb63eadc8757a1..c0c61206499e6bd5 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -1501,6 +1501,7 @@ config BOOT_CONFIG_EMBED_FILE
>
> config INITRAMFS_PRESERVE_MTIME
> bool "Preserve cpio archive mtimes in initramfs"
> + depends on BLK_DEV_INITRD
> default y
> help
> Each entry in an initramfs cpio archive carries an mtime
> value. When
next prev parent reply other threads:[~2025-09-15 11:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 7:11 [PATCH] init: INITRAMFS_PRESERVE_MTIME should depend on BLK_DEV_INITRD Geert Uytterhoeven
2025-09-15 8:14 ` David Disseldorp
2025-09-15 11:39 ` Martin Wilck [this message]
2025-09-15 13:02 ` Christian Brauner
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=aa5d1e137ddab12d1fa6beca4279fd9c90ff58dd.camel@suse.com \
--to=mwilck@suse.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=ddiss@suse.de \
--cc=geert+renesas@glider.be \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=safinaskar@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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