[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPnZJGAp-wG+9wDmmisfpxvFbRtXkG-RipAuZe=fi1BWy-3G-Q@mail.gmail.com>
Date: Thu, 9 Oct 2025 11:42:59 +0300
From: Askar Safin <safinaskar@...il.com>
To: Nicolas Schichan <nschichan@...ebox.fr>
Cc: akpm@...ux-foundation.org, andy.shevchenko@...il.com, axboe@...nel.dk,
brauner@...nel.org, cyphar@...har.com, devicetree@...r.kernel.org,
ecurtin@...hat.com, email2tema@...il.com, graf@...zon.com,
gregkh@...uxfoundation.org, hca@...ux.ibm.com, hch@....de,
hsiangkao@...ux.alibaba.com, initramfs@...r.kernel.org, jack@...e.cz,
julian.stecklina@...erus-technology.de, kees@...nel.org,
linux-acpi@...r.kernel.org, linux-alpha@...r.kernel.org,
linux-api@...r.kernel.org, linux-arch@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-block@...r.kernel.org,
linux-csky@...r.kernel.org, linux-doc@...r.kernel.org,
linux-efi@...r.kernel.org, linux-ext4@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-hexagon@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-m68k@...ts.linux-m68k.org,
linux-mips@...r.kernel.org, linux-openrisc@...r.kernel.org,
linux-parisc@...r.kernel.org, linux-riscv@...ts.infradead.org,
linux-s390@...r.kernel.org, linux-sh@...r.kernel.org,
linux-snps-arc@...ts.infradead.org, linux-um@...ts.infradead.org,
linuxppc-dev@...ts.ozlabs.org, loongarch@...ts.linux.dev, mcgrof@...nel.org,
mingo@...hat.com, monstr@...str.eu, mzxreary@...inter.de,
patches@...ts.linux.dev, rob@...dley.net, sparclinux@...r.kernel.org,
thomas.weissschuh@...utronix.de, thorsten.blum@...ux.dev,
torvalds@...ux-foundation.org, tytso@....edu, viro@...iv.linux.org.uk,
x86@...nel.org
Subject: Re: [PATCH RESEND 00/62] initrd: remove classic initrd support
On Mon, Sep 22, 2025 at 5:29 PM Nicolas Schichan <nschichan@...ebox.fr> wrote:
> > Then in September 2026 I will fully remove initrd.
>
> Is there a way to find some kind of middle ground here ?
I still plan to fully remove initrd in September 2026.
Maintainers will decide whether they will merge my patchset.
You may try to convince them.
> I can send a patch for that but first I need to sort out my SMTP
> issues from the other day.
If you still have mail issues, consider applying for @linux.dev email,
they are free for Linux devs ( https://linux.dev/ ).
Also, I just tried to test whether your use case is still supported in
mainline (i. e. uncompressed initrd with root=/dev/ram0).
It turned out that on modern kernels you need to enable
recently introduced CONFIG_BLK_DEV_WRITE_MOUNTED to
make this work.
So, make sure to enable this when upgrading kernel.
--
Askar Safin
Powered by blists - more mailing lists