reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Lafreniere <peter@n8pjl.ca>
To: geert@linux-m68k.org
Cc: jack@suse.cz, linux-kernel@vger.kernel.org,
	linux-m68k@lists.linux-m68k.org, peter@n8pjl.ca,
	reiserfs-devel@vger.kernel.org
Subject: Re: [PATCH 5/7] arch: m68k: remove ReiserFS from defconfig
Date: Tue, 19 Sep 2023 13:32:33 +0000	[thread overview]
Message-ID: <20230919133227.6448-1-peter@n8pjl.ca> (raw)
In-Reply-To: <CAMuHMdVQaBBZgSsgZyNR2HxMsck2fWNjG6fK93eBFFeyDz0Hkw@mail.gmail.com>

On Mon, Sep 19, 2023 at 03:19, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> Hi Peter,
> 
> On Mon, Sep 18, 2023 at 7:57 PM Peter Lafreniere peter@n8pjl.ca wrote:
> 
> > ReiserFS has been deprecated for a year and a half, yet is still built
> > as part of a defconfig kernel.
> > 
> > According to commit eb103a51640e ("reiserfs: Deprecate reiserfs"), the
> > filesystem is slated to be removed in 2025. Remove it from the defconfig
> > profiles now, as part of its deprecation process.
> > 
> > Signed-off-by: Peter Lafreniere peter@n8pjl.ca
> 
> 
> Thanks for your patch!
> 
> Given these defconfigs enable ReiserFS as a module (not built-in),
> and that ReiserFS is still available upstream, and enabled by distros
> like Debian, I would like to keep it that way.
> The m68k defconfigs will be updated after the removal of ReiserFS,
> as part of the regular defconfig resync.

I still think that since ReiserFS is being removed soon enough and that there
are a negligible number of users, it should be left out of defconfig builds.
allmodconfig and custom configs (like Debian's) exist for a reason.

But yours is a reasonable approach anyhow. Especially for an arch that is in
the same position as some of the more exotic filesystems that you build as
modules. Thanks for taking a look.

Cheers,

Peter Lafreniere
<peter@n8pjl.ca>


  reply	other threads:[~2023-09-19 13:32 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 [this message]
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 ` (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=20230919133227.6448-1-peter@n8pjl.ca \
    --to=peter@n8pjl.ca \
    --cc=geert@linux-m68k.org \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=reiserfs-devel@vger.kernel.org \
    /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).