From: Christoph Hellwig <hch@lst.de>
To: Askar Safin <safinaskar@zohomail.com>
Cc: hch@lst.de, gregkh@linuxfoundation.org,
julian.stecklina@cyberus-technology.de,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
rafael@kernel.org, torvalds@linux-foundation.org,
viro@zeniv.linux.org.uk,
"Gao Xiang" <hsiangkao@linux.alibaba.com>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Subject: Re: [PATCH] initrd: support erofs as initrd
Date: Tue, 26 Aug 2025 09:59:10 +0200 [thread overview]
Message-ID: <20250826075910.GA22903@lst.de> (raw)
In-Reply-To: <20250825182713.2469206-1-safinaskar@zohomail.com>
On Mon, Aug 25, 2025 at 09:27:13PM +0300, Askar Safin wrote:
> > We've been trying to kill off initrd in favor of initramfs for about
> > two decades. I don't think adding new file system support to it is
> > helpful.
>
> I totally agree.
>
> What prevents us from removing initrd right now?
>
> The only reason is lack of volunteers?
>
> If yes, then may I remove initrd?
Give it a spin and see if anyone shouts.
next prev parent reply other threads:[~2025-08-26 7:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 19:28 [PATCH] initrd: support erofs as initrd Julian Stecklina
2025-03-20 19:28 ` Julian Stecklina via B4 Relay
2025-03-21 2:08 ` Al Viro
2025-03-21 8:46 ` Christian Brauner
2025-03-21 12:49 ` Julian Stecklina
2025-03-21 5:01 ` Christoph Hellwig
2025-03-21 5:27 ` Gao Xiang
2025-03-21 13:17 ` Julian Stecklina
2025-03-21 13:57 ` Gao Xiang
2025-04-07 8:57 ` hch
2025-04-07 11:19 ` Julian Stecklina
2025-04-07 16:05 ` Gao Xiang
2025-08-25 18:27 ` Askar Safin
2025-08-26 7:59 ` Christoph Hellwig [this message]
2025-08-26 14:21 ` Byron Stanoszek
2025-08-26 15:32 ` Gao Xiang
2025-08-26 16:00 ` Gao Xiang
2025-08-27 9:22 ` Askar Safin
2025-08-27 9:48 ` Gao Xiang
2025-08-27 9:58 ` Gao Xiang
2025-08-28 16:44 ` Askar Safin
2025-08-28 17:00 ` Gao Xiang
2025-08-28 17:14 ` Gao Xiang
2025-08-30 11:49 ` Askar Safin
2025-08-30 12:23 ` Gao Xiang
2025-08-26 17:00 ` Askar Safin
2025-03-21 8:48 ` Christian Brauner
2025-03-21 9:16 ` Thomas Weißschuh
2025-03-21 13:26 ` Julian Stecklina
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=20250826075910.GA22903@lst.de \
--to=hch@lst.de \
--cc=gregkh@linuxfoundation.org \
--cc=hsiangkao@linux.alibaba.com \
--cc=julian.stecklina@cyberus-technology.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=safinaskar@zohomail.com \
--cc=thomas.weissschuh@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.