reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Lafreniere <peter@n8pjl.ca>
To: geert@linux-m68k.org, jack@suse.cz
Cc: anton.ivanov@cambridgegreys.com, johannes@sipsolutions.net,
	linux-um@lists.infradead.org, peter@n8pjl.ca,
	reiserfs-devel@vger.kernel.org, richard@nod.at
Subject: Re: [PATCH RESEND] um: Remove CONFIG_REISERFS_FS from defconfig
Date: Mon, 18 Sep 2023 16:32:48 +0000	[thread overview]
Message-ID: <20230918163234.8514-1-peter@n8pjl.ca> (raw)
In-Reply-To: <20230918132614.zmmuc72purc2psik@quack3>

On Monday, September 18th, 2023 at 09:26, 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?

I agree. I can send a patch series for those arches except for ia64, which has
already been removed from linux-next.

> 
> Honza
> 
> > ---
> > Fixed invalid DKIM settings causing the previous patch to be rejected.
> > 
> > arch/um/configs/i386_defconfig | 1 -
> > arch/um/configs/x86_64_defconfig | 1 -
> > 2 files changed, 2 deletions(-)
> > 
> > diff --git a/arch/um/configs/i386_defconfig b/arch/um/configs/i386_defconfig
> > index e543cbac8792..9c9c77f1255a 100644
> > --- a/arch/um/configs/i386_defconfig
> > +++ b/arch/um/configs/i386_defconfig
> > @@ -61,7 +61,6 @@ CONFIG_UML_NET_DAEMON=y
> > CONFIG_UML_NET_MCAST=y
> > CONFIG_UML_NET_SLIRP=y
> > CONFIG_EXT4_FS=y
> > -CONFIG_REISERFS_FS=y
> > CONFIG_QUOTA=y
> > CONFIG_AUTOFS_FS=m
> > CONFIG_ISO9660_FS=m
> > diff --git a/arch/um/configs/x86_64_defconfig b/arch/um/configs/x86_64_defconfig
> > index 939cb12318ca..03b10d3f6816 100644
> > --- a/arch/um/configs/x86_64_defconfig
> > +++ b/arch/um/configs/x86_64_defconfig
> > @@ -59,7 +59,6 @@ CONFIG_UML_NET_DAEMON=y
> > CONFIG_UML_NET_MCAST=y
> > CONFIG_UML_NET_SLIRP=y
> > CONFIG_EXT4_FS=y
> > -CONFIG_REISERFS_FS=y
> > CONFIG_QUOTA=y
> > CONFIG_AUTOFS_FS=m
> > CONFIG_ISO9660_FS=m
> > --
> > 2.42.0
> 
> --
> Jan Kara jack@suse.com
> 
> SUSE Labs, CRi

      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
2023-09-18 16:35       ` Peter Lafreniere
2023-09-18 16:40         ` Peter Lafreniere
2023-09-18 16:32     ` Peter Lafreniere [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=20230918163234.8514-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 NNTP newsgroup(s).