From: Jan Kara <jack@suse.cz>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jan Kara <jack@suse.cz>, Peter Lafreniere <peter@n8pjl.ca>,
linux-um@lists.infradead.org, richard@nod.at,
anton.ivanov@cambridgegreys.com, johannes@sipsolutions.net,
reiserfs-devel@vger.kernel.org
Subject: Re: [PATCH RESEND] um: Remove CONFIG_REISERFS_FS from defconfig
Date: Mon, 18 Sep 2023 18:32:07 +0200 [thread overview]
Message-ID: <20230918163207.3e2hev3zxnr3bakj@quack3> (raw)
In-Reply-To: <CAMuHMdWzN0Gs2FTQDFeBLz2498dv3ZYCBL2xOvL5YdHAveaH9g@mail.gmail.com>
On Mon 18-09-23 16:58:05, Geert Uytterhoeven wrote:
> Hi Jan,
>
> On Mon, Sep 18, 2023 at 3:26 PM Jan Kara <jack@suse.cz> wrote:
> > On Mon 18-09-23 12:58:26, Peter Lafreniere wrote:
> > > ReiserFS has been deprecated for a year and a half, yet is still built
> > > as part of a defconfig UML kernel.
> > >
> > > According to commit eb103a51640e ("reiserfs: Deprecate reiserfs"), the
> > > filesystem is slated to be removed in 2025. Remove it from the defconfig
> > > profile now, as part of its deprecation process.
> > >
> > > Signed-off-by: Peter Lafreniere <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.
There's no need to change if you don't want to. I can just imagine how for
other archs which seem to enable only "useful" filesystems in defconfig
disabling a deprecated filesystem makes sense.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
_______________________________________________
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-18 16:32 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 [this message]
2023-09-18 16:35 ` Peter Lafreniere
2023-09-18 16:40 ` Peter Lafreniere
2023-09-18 16:32 ` [PATCH RESEND] " 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=20230918163207.3e2hev3zxnr3bakj@quack3 \
--to=jack@suse.cz \
--cc=anton.ivanov@cambridgegreys.com \
--cc=geert@linux-m68k.org \
--cc=johannes@sipsolutions.net \
--cc=linux-um@lists.infradead.org \
--cc=peter@n8pjl.ca \
--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 NNTP newsgroup(s).