From: Richard Cheng <icheng@nvidia•com>
To: Krzysztof Kozlowski <krzk@kernel•org>
Cc: Arnd Bergmann <arnd@arndb•de>,
soc@lists•linux.dev, Russell King <linux@armlinux•org.uk>,
Theodore Ts'o <tytso@mit•edu>,
linux-arm-kernel@lists•infradead.org,
linux-kernel@vger•kernel.org
Subject: Re: [PATCH] ARM: configs: Drop duplicated CONFIG_EXT4_FS
Date: Wed, 3 Jun 2026 17:47:00 +0800 [thread overview]
Message-ID: <ah_3BtqexORj57-2@MWDK4CY14F> (raw)
In-Reply-To: <ccd048c2-ee82-481a-b948-9f5e5e114c25@kernel.org>
On Wed, Jun 03, 2026 at 11:12:45AM +0800, Krzysztof Kozlowski wrote:
> On 03/06/2026 10:59, Richard Cheng wrote:
>
> Please kindly trim the replies from unnecessary context. It makes it
> much easier to find new content.
>
> >> --
> >> 2.53.0
> >>
> >>
> >
> > Hi Krzysztof,
> >
> > LGTM.
> > Though I wonder which compiler did you use and how did you encounter
> > the warning? on what system if you may share with us?
>
> I am confused with above questions and it feels like the review might
> not be applicable in such case. You do understand this is a defconfig?
>
Hi Krzysztof,
You're right, my mistake. I conflated it with a compiler diagnostic.
The warning comes from Kconfig, so it reproduces on any host that run
the corresponding defconfig, regardless of the toolchain.
The questions don't apply.
Best regards,
Richard Cheng.
prev parent reply other threads:[~2026-06-03 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 7:27 [PATCH] ARM: configs: Drop duplicated CONFIG_EXT4_FS Krzysztof Kozlowski
2026-06-03 8:59 ` Richard Cheng
2026-06-03 9:12 ` Krzysztof Kozlowski
2026-06-03 9:47 ` Richard Cheng [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=ah_3BtqexORj57-2@MWDK4CY14F \
--to=icheng@nvidia$(echo .)com \
--cc=arnd@arndb$(echo .)de \
--cc=krzk@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux@armlinux$(echo .)org.uk \
--cc=soc@lists$(echo .)linux.dev \
--cc=tytso@mit$(echo .)edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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