From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Maxime Ripard <mripard@redhat.com>, Arnd Bergmann <arnd@arndb.de>
Cc: Javier Martinez Canillas <javierm@redhat.com>,
linux-kernel@vger.kernel.org,
Enric Balletbo i Serra <eballetbo@redhat.com>,
Erico Nunes <nunes.erico@gmail.com>,
Brian Masney <bmasney@redhat.com>,
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 16:53:26 +0100 [thread overview]
Message-ID: <8ad96253-2053-4dc1-8dc1-d01d1fa36877@linaro.org> (raw)
In-Reply-To: <724jnhrbs6r4q6whynr3aon5w7mhfvetlgcnts4nukvtxbuium@mrjv6apjqk7r>
On 21/02/2024 16:51, Maxime Ripard wrote:
>>> Sure, but you're not just arguing for XFS there.
>>>
>>> What I really don't get is this: this makes the life of people easier.
>>>
>>> Being able to test an upstream kernel quickly when you have a bug in a
>>> downstream distro is super valuable for any distro developper. And on
>>> the long run, if we don't make the switch from a kernel distro to a
>>> mainline kernel relatively easy, we're the ones that will lose out.
>>> Because people just won't bother, or be frustrated and thus super
>>> reluctant to do that work.
>>
>> We had previously discussed adding config fragments for common
>> distros the way we have kvm_guest.config, but if the Javier's
>> patch is all that is actually needed for Fedora, that seems better
>> to me than the added complexity of fragments.
>
> Oh, right. Fragments would be a great tool to reconcile the need for
> minimal boot time and supporting reasonable use-cases.
>
> I guess it's even more of a struggle with the single arm64 defconfig vs
> the minimal vs batteries included defconfig setup we had for arm.
It would be cool to group also all the per-SoC needs in dedicated
fragments...
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-02-21 15:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 14:13 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 [this message]
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
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=8ad96253-2053-4dc1-8dc1-d01d1fa36877@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=arnd@arndb.de \
--cc=bmasney@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=eballetbo@redhat.com \
--cc=geert+renesas@glider.be \
--cc=javierm@redhat.com \
--cc=konrad.dybcio@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
all inboxes | Powered by JetHome®