From: Peter Lafreniere <peter@n8pjl.ca>
To: geert@linux-m68k.org
Cc: anton.ivanov@cambridgegreys.com, ink@jurassic.park.msu.ru,
jack@suse.cz, johannes@sipsolutions.net,
linux-alpha@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-m68k@vger.kernel.org,
linux-mips@vger.kernel.org, linux-sh@vger.kernel.org,
linux-um@lists.infradead.org, linux@armlinux.org.uk,
linuxppc-dev@lists.ozlabs.org, peter@n8pjl.ca,
reiserfs-devel@vger.kernel.org, richard.henderson@linaro.org,
richard@nod.at, segher@kernel.crashing.org,
tsbogend@alpha.franken.de
Subject: Re: [PATCH 0/7] arch/*: config: Remove ReiserFS from defconfig
Date: Tue, 19 Sep 2023 16:15:41 +0000 [thread overview]
Message-ID: <20230919161535.4774-1-peter@n8pjl.ca> (raw)
In-Reply-To: <CAMuHMdXQ=xpeY3tmLXe1kgJbRtmVAn62rEhvzO+VB7GCgy4F8w@mail.gmail.com>
Hi Geert,
On Tue, Sep 19, 2023 at 12:02, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
> Hi Peter,
>
> On Tue, Sep 19, 2023 at 5:58 PM Peter Lafreniere peter@n8pjl.ca wrote:
>
> > 2) Stops building an obsolete and largely-unused filesystem unnecessarily.
> > Some hobbyist targets like m68k and alpha may prefer to keep all filesystems
> > available until total removal, but others like arm and UML have no need for
> > ReiserFS to be built unless specifically configured.
>
>
> As UML is used a lot for testing, isn't it actually counter-productive
> to remove ReiserFS from the UML defconfig? The less testing it
> receives, the higher the chance of introducing regressions.
UML is used for testing, but in my view that makes the inclusion of
ReiserFS in its defconfig even worse. Users of UML are trying to test a
particular function, and so tend to use ext[2-4], as those are included in
the defconfig and are well tested and stable. So there is no extra testing
being done on ReiserFS due to its inclusion in the defconfig.
Keeping UML's defconfig as slim as possible improves build times, which is
particularly important for kernel testing and development.
>
> Gr{oetje,eeting}s,
>
> Geert
>
Cheers,
Peter Lafreniere
next prev parent reply other threads:[~2023-09-19 16:15 UTC|newest]
Thread overview: 11+ 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:57 ` [PATCH 7/7] arch: alpha: remove " 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 [this message]
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=20230919161535.4774-1-peter@n8pjl.ca \
--to=peter@n8pjl.ca \
--cc=anton.ivanov@cambridgegreys.com \
--cc=geert@linux-m68k.org \
--cc=ink@jurassic.park.msu.ru \
--cc=jack@suse.cz \
--cc=johannes@sipsolutions.net \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=richard.henderson@linaro.org \
--cc=richard@nod.at \
--cc=segher@kernel.crashing.org \
--cc=tsbogend@alpha.franken.de \
/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).