From: Peter Lafreniere <peter@n8pjl.ca>
To: peter@n8pjl.ca
Cc: anton.ivanov@cambridgegreys.com, geert@linux-m68k.org,
jack@suse.cz, johannes@sipsolutions.net,
linux-um@lists.infradead.org, reiserfs-devel@vger.kernel.org,
richard@nod.at
Subject: um: Remove CONFIG_REISERFS_FS from defconfig
Date: Mon, 18 Sep 2023 16:40:22 +0000 [thread overview]
Message-ID: <20230918164017.8827-1-peter@n8pjl.ca> (raw)
In-Reply-To: <20230918163544.8604-1-peter@n8pjl.ca>
> > > Makes sense but I've noticed there are many more architectures that define
> > > CONFIG_REISERFS_FS in their defconfig (sh, powerpc, mips, m68k, ia64, arm,
> > > alpha). So perhaps we should do this for all of them when we are at it?
> >
> > The policy for the m68k defconfigs is to enable all available exotic
> > file systems as modules, so support for them is available when needed.
> >
> > Please let me know why this should be changed, as long as ReiserFS is
> > still available in the upstream kernel.
>
>
> I understand that policy and it makes particular sense for older/hobbyist
> hardware like the m68k classic where ReiserFS is included in make defconfig.
>
> However, ReiserFS is deprecated and should be phased out as best as possible
> before its removal, and pruning config options for a filesystem that is
> considered obsolete and should not be used on the newest kernels is a step
> towards that.
>
> ReiserFS is still availiable to be configured by anyone who builds their own
> kernel and is still availiable in all(mod|yes)config. As such I can justify
> the removal of some old config options that doesn't actually remove support for
> the filesystem when it simplifies the deprecation and removal processes for an
> ancient, largely unused filesystem.
>
> Please remember that users who build and install their own kernel on hobbyist
> hardware should be capable enough to select one Kconfig option if they happen to
> need ReiserFS. If not, then removing ReiserFS from the defconfig on a kernel
> update is an easier issue to work around than waiting to remove the filesystem
> from the tree entirely.
Though as Jan said, you're free to not accept a patch removing the config option
until the filesystem is gone for good. I just feel like it's easier to remove
ReiserFS from all defconfigs in one fell swoop.
Cheers,
Peter Lafreniere
<peter@n8pjl.ca>
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2023-09-23 15:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 23:26 [PATCH] um: Remove CONFIG_REISERFS_FS from defconfig Peter Lafreniere
2023-09-18 12:58 ` [PATCH RESEND] " Peter Lafreniere
2023-09-18 13:26 ` Jan Kara
2023-09-18 13:58 ` Richard Weinberger
2023-09-18 14:14 ` Peter Lafreniere
2023-09-18 14:24 ` Jan Kara
2023-09-18 14:58 ` Geert Uytterhoeven
2023-09-18 16:32 ` Jan Kara
2023-09-18 16:35 ` Peter Lafreniere
2023-09-18 16:40 ` Peter Lafreniere [this message]
2023-09-18 16:32 ` Peter Lafreniere
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=20230918164017.8827-1-peter@n8pjl.ca \
--to=peter@n8pjl.ca \
--cc=anton.ivanov@cambridgegreys.com \
--cc=geert@linux-m68k.org \
--cc=jack@suse.cz \
--cc=johannes@sipsolutions.net \
--cc=linux-um@lists.infradead.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=richard@nod.at \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).