From: Javier Martinez Canillas <javierm@redhat.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-kernel@vger.kernel.org
Cc: Enric Balletbo i Serra <eballetbo@redhat.com>,
Maxime Ripard <mripard@redhat.com>,
Erico Nunes <nunes.erico@gmail.com>,
Brian Masney <bmasney@redhat.com>, Arnd Bergmann <arnd@arndb.de>,
Bjorn Andersson <quic_bjorande@quicinc.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] arm64: defconfig: Enable zram, xfs and loading compressed FW support
Date: Wed, 21 Feb 2024 15:55:04 +0100 [thread overview]
Message-ID: <87a5ntj29j.fsf@minerva.mail-host-address-is-not-set> (raw)
In-Reply-To: <1f28256c-e436-4add-aa67-2cfb2248b220@linaro.org>
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> writes:
> On 21/02/2024 15:13, Javier Martinez Canillas wrote:
>> These options are needed by some Linux distributions (e.g: Fedora), so
>
> How ZRAM is needed? Why Fedora cannot boot without it? Debian, which I
> use on my arm64 boards, does not have any problem.
>
I haven't used Debian in ages so I don't know why is not a problem there.
But Fedora is using zram by default and if is not enabled in the kernel,
the boot is delayed considerably due the systemd zram-generator.
> I kind of repeat comments from similar patch earlier:
> https://lore.kernel.org/all/fe1e74a2-e933-7cd9-f740-86d871076191@linaro.org/
>
Ah! I forgot that posted the same change for exynos_defconfig some time
ago and I see that you nacked. Now I understand why all my Exynos boards
are in a drawer.
> About XFS: I don't think it is needed to boot anything.
>
How are you supposed to mount a XFS rootfs without at least have support
for it as a module?
> This is a defconfig, not a distro config. Please don't make it distro.
>
It seems that's a Debian distro config though, since you brought Debian as
an example.
> I will gladly support things needed by systemd or equivalent, but not
> unusual filesystems needed by distro.
>
Fair. But then you should probably remove all the other filesystems that are
already in the defconfig then?
$ grep "_FS=" arch/arm64/configs/defconfig | wc -l
15
Or it is OK to have support for btrfs, overlayfs, even plan9 fs but XFS is
where you draw the line??
> Best regards,
> Krzysztof
>
--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2024-02-21 14:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 14:13 [PATCH v2] arm64: defconfig: Enable zram, xfs and loading compressed FW support Javier Martinez Canillas
2024-02-21 14:22 ` Krzysztof Kozlowski
2024-02-21 14:48 ` Maxime Ripard
2024-02-21 15:10 ` Krzysztof Kozlowski
2024-02-21 15:14 ` Krzysztof Kozlowski
2024-02-21 15:20 ` Geert Uytterhoeven
2024-02-21 15:24 ` Maxime Ripard
2024-02-21 15:38 ` Krzysztof Kozlowski
2024-02-21 19:34 ` Javier Martinez Canillas
2024-02-22 8:40 ` Krzysztof Kozlowski
2024-02-22 9:09 ` Javier Martinez Canillas
2024-02-22 11:17 ` Krzysztof Kozlowski
2024-02-21 15:41 ` Arnd Bergmann
2024-02-21 15:46 ` Krzysztof Kozlowski
2024-02-21 15:51 ` Maxime Ripard
2024-02-21 15:53 ` Krzysztof Kozlowski
2024-02-21 15:56 ` Brian Masney
2024-02-21 16:50 ` Andrew Halaney
2024-02-21 21:56 ` Javier Martinez Canillas
2024-02-21 14:55 ` Javier Martinez Canillas [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=87a5ntj29j.fsf@minerva.mail-host-address-is-not-set \
--to=javierm@redhat.com \
--cc=arnd@arndb.de \
--cc=bmasney@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=eballetbo@redhat.com \
--cc=geert+renesas@glider.be \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mripard@redhat.com \
--cc=neil.armstrong@linaro.org \
--cc=nunes.erico@gmail.com \
--cc=quic_bjorande@quicinc.com \
--cc=will@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