From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Askar Safin <safinaskar@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Christian Brauner" <brauner@kernel.org>,
"Al Viro" <viro@zeniv.linux.org.uk>, "Jan Kara" <jack@suse.cz>,
"Christoph Hellwig" <hch@lst.de>, "Jens Axboe" <axboe@kernel.dk>,
"Aleksa Sarai" <cyphar@cyphar.com>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Julian Stecklina" <julian.stecklina@cyberus-technology.de>,
"Gao Xiang" <hsiangkao@linux.alibaba.com>,
"Art Nikpal" <email2tema@gmail.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Alexander Graf" <graf@amazon.com>,
"Rob Landley" <rob@landley.net>,
"Lennart Poettering" <mzxreary@0pointer.de>,
linux-arch@vger.kernel.org, linux-block@vger.kernel.org,
initramfs@vger.kernel.org, linux-api@vger.kernel.org,
linux-doc@vger.kernel.org, "Michal Simek" <monstr@monstr.eu>,
"Luis Chamberlain" <mcgrof@kernel.org>,
"Kees Cook" <kees@kernel.org>,
"Thorsten Blum" <thorsten.blum@linux.dev>,
"Heiko Carstens" <hca@linux.ibm.com>,
"Arnd Bergmann" <arnd@arndb.de>, "Dave Young" <dyoung@redhat.com>,
"Christophe Leroy" <christophe.leroy@csgroup.eu>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Borislav Petkov" <bp@alien8.de>,
"Jessica Clarke" <jrtc27@jrtc27.com>,
"Nicolas Schichan" <nschichan@freebox.fr>,
"David Disseldorp" <ddiss@suse.de>,
patches@lists.linux.dev
Subject: Re: [PATCH v2 2/3] initrd: remove deprecated code path (linuxrc)
Date: Fri, 10 Oct 2025 18:04:33 +0300 [thread overview]
Message-ID: <CAHp75VezkZ7A1VOP8cBH8h0DKVumP66jjUbepMCP87wGOrh+MQ@mail.gmail.com> (raw)
In-Reply-To: <20251010094047.3111495-3-safinaskar@gmail.com>
On Fri, Oct 10, 2025 at 12:42 PM Askar Safin <safinaskar@gmail.com> wrote:
>
> Remove linuxrc initrd code path, which was deprecated in 2020.
>
> Initramfs and (non-initial) RAM disks (i. e. brd) still work.
>
> Both built-in and bootloader-supplied initramfs still work.
>
> Non-linuxrc initrd code path (i. e. using /dev/ram as final root
> filesystem) still works, but I put deprecation message into it
...
> - noinitrd [RAM] Tells the kernel not to load any configured
> + noinitrd [Deprecated,RAM] Tells the kernel not to load any configured
> initial RAM disk.
How one is supposed to run this when just having a kernel is enough?
At least (ex)colleague of mine was a heavy user of this option for
testing kernel builds on the real HW.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-10-10 15:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 9:40 [PATCH v2 0/3] initrd: remove half of classic initrd support Askar Safin
2025-10-10 9:40 ` [PATCH v2 1/3] init: remove deprecated "load_ramdisk" and "prompt_ramdisk" command line parameters Askar Safin
2025-10-10 15:02 ` Andy Shevchenko
2025-10-13 6:05 ` Askar Safin
2025-10-10 9:40 ` [PATCH v2 2/3] initrd: remove deprecated code path (linuxrc) Askar Safin
2025-10-10 15:04 ` Andy Shevchenko [this message]
2025-10-13 9:59 ` Askar Safin
2025-10-10 19:31 ` Randy Dunlap
2025-10-13 10:29 ` Askar Safin
2025-10-10 9:40 ` [PATCH v2 3/3] init: remove /proc/sys/kernel/real-root-dev Askar Safin
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=CAHp75VezkZ7A1VOP8cBH8h0DKVumP66jjUbepMCP87wGOrh+MQ@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=bp@alien8.de \
--cc=brauner@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=cyphar@cyphar.com \
--cc=ddiss@suse.de \
--cc=dyoung@redhat.com \
--cc=email2tema@gmail.com \
--cc=graf@amazon.com \
--cc=gregkh@linuxfoundation.org \
--cc=hca@linux.ibm.com \
--cc=hch@lst.de \
--cc=hsiangkao@linux.alibaba.com \
--cc=initramfs@vger.kernel.org \
--cc=jack@suse.cz \
--cc=jrtc27@jrtc27.com \
--cc=julian.stecklina@cyberus-technology.de \
--cc=kees@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=monstr@monstr.eu \
--cc=mzxreary@0pointer.de \
--cc=nschichan@freebox.fr \
--cc=patches@lists.linux.dev \
--cc=rob@landley.net \
--cc=safinaskar@gmail.com \
--cc=thomas.weissschuh@linutronix.de \
--cc=thorsten.blum@linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).