Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:8 as permitted sender) client-ip=2620:137:e000::3:8;
Date:   Tue, 19 Sep 2023 13:32:33 +0000
To:     geert@linux-m68k.org
From:   Peter Lafreniere <peter@n8pjl.ca>
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
Message-ID: <20230919133227.6448-1-peter@n8pjl.ca>
In-Reply-To: <CAMuHMdVQaBBZgSsgZyNR2HxMsck2fWNjG6fK93eBFFeyDz0Hkw@mail.gmail.com>
References: <20230918175529.19011-1-peter@n8pjl.ca> <20230918175529.19011-6-peter@n8pjl.ca> <CAMuHMdVQaBBZgSsgZyNR2HxMsck2fWNjG6fK93eBFFeyDz0Hkw@mail.gmail.com>
Feedback-ID: 53133685:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Mon, Sep 19, 2023 at 03:19, Geert Uytterhoeven <geert@linux-m68k.org> wr=
ote:
> Hi Peter,
>=20
> On Mon, Sep 18, 2023 at 7:57=E2=80=AFPM Peter Lafreniere peter@n8pjl.ca w=
rote:
>=20
> > ReiserFS has been deprecated for a year and a half, yet is still built
> > as part of a defconfig kernel.
> >=20
> > According to commit eb103a51640e ("reiserfs: Deprecate reiserfs"), the
> > filesystem is slated to be removed in 2025. Remove it from the defconfi=
g
> > profiles now, as part of its deprecation process.
> >=20
> > Signed-off-by: Peter Lafreniere peter@n8pjl.ca
>=20
>=20
> Thanks for your patch!
>=20
> 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 the=
re
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 i=
n
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>