From: Askar Safin <safinaskar@gmail.com>
To: bagasdotme@gmail.com
Cc: akpm@linux-foundation.org, andy.shevchenko@gmail.com,
arnd@arndb.de, axboe@kernel.dk, bp@alien8.de, brauner@kernel.org,
christophe.leroy@csgroup.eu, cyphar@cyphar.com, ddiss@suse.de,
dyoung@redhat.com, email2tema@gmail.com, graf@amazon.com,
gregkh@linuxfoundation.org, hca@linux.ibm.com, hch@lst.de,
hsiangkao@linux.alibaba.com, initramfs@vger.kernel.org,
jack@suse.cz, jrtc27@jrtc27.com,
julian.stecklina@cyberus-technology.de, kees@kernel.org,
krzk@kernel.org, linux-api@vger.kernel.org,
linux-arch@vger.kernel.org, linux-block@vger.kernel.org,
linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, mcgrof@kernel.org,
monstr@monstr.eu, mzxreary@0pointer.de, nschichan@freebox.fr,
patches@lists.linux.dev, rob@landley.net, safinaskar@gmail.com,
thomas.weissschuh@linutronix.de, thorsten.blum@linux.dev,
torvalds@linux-foundation.org, viro@zeniv.linux.org.uk
Subject: Re: [PATCH v3 2/3] initrd: remove deprecated code path (linuxrc)
Date: Wed, 22 Oct 2025 11:06:25 +0300 [thread overview]
Message-ID: <20251022080626.24446-1-safinaskar@gmail.com> (raw)
In-Reply-To: <aPg-YF2pcyI-HusN@archie.me>
Bagas Sanjaya <bagasdotme@gmail.com>:
> Do you mean that initrd support will be removed in LTS kernel release of 2026?
I meant September 2026. But okay, if there is v4, then I will change this to
"after LTS release in the end of 2026".
--
Askar Safin
next prev parent reply other threads:[~2025-10-22 8:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 6:09 [PATCH v3 0/3] initrd: remove half of classic initrd support Askar Safin
2025-10-17 6:09 ` [PATCH v3 1/3] init: remove deprecated "load_ramdisk" and "prompt_ramdisk" command line parameters Askar Safin
2025-10-17 6:09 ` [PATCH v3 2/3] initrd: remove deprecated code path (linuxrc) Askar Safin
2025-10-22 2:16 ` Bagas Sanjaya
2025-10-22 8:06 ` Askar Safin [this message]
2025-10-22 16:41 ` Andy Shevchenko
2025-10-17 6:09 ` [PATCH v3 3/3] init: remove /proc/sys/kernel/real-root-dev Askar Safin
2025-10-21 13:05 ` [PATCH v3 0/3] initrd: remove half of classic initrd support Christian Brauner
2025-10-22 6:44 ` Christoph Hellwig
2025-10-22 8:26 ` 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=20251022080626.24446-1-safinaskar@gmail.com \
--to=safinaskar@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=bagasdotme@gmail.com \
--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=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).