From: Segher Boessenkool <segher@kernel.crashing.org>
To: Peter Lafreniere <peter@n8pjl.ca>
Cc: linux-m68k@vger.kernel.org, tsbogend@alpha.franken.de,
jack@suse.cz, linux-sh@vger.kernel.org, linux@armlinux.org.uk,
richard@nod.at, linux-um@lists.infradead.org,
reiserfs-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
richard.henderson@linaro.org, ink@jurassic.park.msu.ru,
linux-alpha@vger.kernel.org, geert@linux-m68k.org,
johannes@sipsolutions.net, linux-mips@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
anton.ivanov@cambridgegreys.com
Subject: Re: [PATCH 0/7] arch/*: config: Remove ReiserFS from defconfig
Date: Mon, 18 Sep 2023 18:41:08 -0500 [thread overview]
Message-ID: <20230918234108.GN19790@gate.crashing.org> (raw)
In-Reply-To: <20230918175529.19011-1-peter@n8pjl.ca>
On Mon, Sep 18, 2023 at 05:56:09PM +0000, Peter Lafreniere wrote:
> ReiserFS has been considered deprecated for 19 months since commit
> eb103a51640e ("reiserfs: Deprecate reiserfs"). However, there are
> several architectures that still build it into their defconfig kernels.
>
> As ReiserFS will be removed in 2025, delete all ReiserFS-related options
> from defconfig files before the filesystem's removal.
This is essentially equivalent to deleting the filesystem now. Why do
this? Is there such a hurry?
Segher
next prev parent reply other threads:[~2023-09-18 23:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 17:56 [PATCH 0/7] arch/*: config: Remove ReiserFS from defconfig Peter Lafreniere
2023-09-18 17:56 ` [PATCH 2/7] arch: powerpc: remove " Peter Lafreniere
2023-09-18 23:41 ` Segher Boessenkool [this message]
2023-09-19 0:00 ` [PATCH 0/7] arch/*: config: Remove " Peter Lafreniere
2023-09-19 15:16 ` Segher Boessenkool
2023-09-19 15:58 ` Peter Lafreniere
2023-09-19 16:02 ` Geert Uytterhoeven
2023-09-19 16:15 ` Peter Lafreniere
2023-09-20 9:30 ` Geert Uytterhoeven
2023-09-20 16:56 ` Jan Kara
2023-10-15 10:04 ` (subset) " Michael Ellerman
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=20230918234108.GN19790@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=anton.ivanov@cambridgegreys.com \
--cc=geert@linux-m68k.org \
--cc=ink@jurassic.park.msu.ru \
--cc=jack@suse.cz \
--cc=johannes@sipsolutions.net \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=peter@n8pjl.ca \
--cc=reiserfs-devel@vger.kernel.org \
--cc=richard.henderson@linaro.org \
--cc=richard@nod.at \
--cc=tsbogend@alpha.franken.de \
/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).