From: Michael Ellerman <mpe@ellerman.id.au>
To: reiserfs-devel@vger.kernel.org, Peter Lafreniere <peter@n8pjl.ca>
Cc: jack@suse.cz, linux-kernel@vger.kernel.org, richard@nod.at,
anton.ivanov@cambridgegreys.com, johannes@sipsolutions.net,
linuxppc-dev@lists.ozlabs.org, linux-um@lists.infradead.org,
linux-sh@vger.kernel.org, tsbogend@alpha.franken.de,
linux-mips@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
geert@linux-m68k.org, linux-arm-kernel@lists.infradead.org,
linux@armlinux.org.uk, linux-alpha@vger.kernel.org,
richard.henderson@linaro.org, ink@jurassic.park.msu.ru
Subject: Re: (subset) [PATCH 0/7] arch/*: config: Remove ReiserFS from defconfig
Date: Sun, 15 Oct 2023 21:04:58 +1100 [thread overview]
Message-ID: <169736429854.960528.1442206910501555108.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20230918175529.19011-1-peter@n8pjl.ca>
On Mon, 18 Sep 2023 17:56:09 +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.
>
> [...]
Applied to powerpc/next.
[2/7] arch: powerpc: remove ReiserFS from defconfig
https://git.kernel.org/powerpc/c/c945e6f453a361b0e9daddd2be9c099d1b80d6f8
cheers
prev parent reply other threads:[~2023-10-15 10:06 UTC|newest]
Thread overview: 21+ 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 1/7] arch: um: remove " Peter Lafreniere
2023-09-18 17:56 ` [PATCH 2/7] arch: powerpc: " Peter Lafreniere
2023-09-18 17:56 ` [PATCH 3/7] arch: sh: " Peter Lafreniere
2023-10-24 16:46 ` John Paul Adrian Glaubitz
2023-10-24 17:45 ` Peter Lafreniere
2023-09-18 17:57 ` [PATCH 4/7] arch: mips: " Peter Lafreniere
2023-09-18 17:57 ` [PATCH 5/7] arch: m68k: " Peter Lafreniere
2023-09-19 7:19 ` Geert Uytterhoeven
2023-09-19 13:32 ` Peter Lafreniere
2023-09-18 17:57 ` [PATCH 6/7] arch: arm: " Peter Lafreniere
2023-09-18 17:57 ` [PATCH 7/7] arch: alpha: " Peter Lafreniere
2023-09-18 23:41 ` [PATCH 0/7] arch/*: config: Remove " Segher Boessenkool
2023-09-19 0:00 ` 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 ` Michael Ellerman [this message]
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=169736429854.960528.1442206910501555108.b4-ty@ellerman.id.au \
--to=mpe@ellerman.id.au \
--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@lists.linux-m68k.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).