From: Krzysztof Kozlowski <krzk@kernel.org>
To: Umang Chheda <umang.chheda@oss.qualcomm.com>,
andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
richardcochran@gmail.com
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, mohd.anwar@oss.qualcomm.com,
krishna.chundru@oss.qualcomm.com,
monish.chunara@oss.qualcomm.com
Subject: Re: [PATCH v3 1/1] arm64: dts: qcom: lemans-evk: Add Mezzanine
Date: Mon, 23 Feb 2026 15:41:49 +0100 [thread overview]
Message-ID: <57424679-5ed3-457a-b336-d468983c144e@kernel.org> (raw)
In-Reply-To: <628df86f-e866-4986-a1a6-8c1b38f3c85f@kernel.org>
On 23/02/2026 14:13, Krzysztof Kozlowski wrote:
>> +
>> + vreg_4p2: regulator-vreg-4p2 {
>> + compatible = "regulator-fixed";
>> + regulator-name = "VREG_4P2";
>> +
>> + regulator-min-microvolt = <4200000>;
>> + regulator-max-microvolt = <4200000>;
>> + regulator-always-on;
>> + regulator-boot-on;
>> +
>> + vin-supply = <&vreg_sys_pwr>;
>> + };
>> +
>> + vreg_sys_pwr: regulator-vreg-sys-pwr {
>
> And here the same pattern as in Monaco EVK. This is pointless, you just
> inflate the kernel and DTS with dummies.
>
>
I found more of such patterns in the code... folks, this is non-sense.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-02-23 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 19:38 [PATCH v3 0/1] Introduce Lemans EVK Peripheral Mezzanine Umang Chheda
2026-02-03 19:38 ` [PATCH v3 1/1] arm64: dts: qcom: lemans-evk: Add Mezzanine Umang Chheda
2026-02-04 9:23 ` Konrad Dybcio
2026-02-23 13:13 ` Krzysztof Kozlowski
2026-02-23 14:41 ` Krzysztof Kozlowski [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=57424679-5ed3-457a-b336-d468983c144e@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krishna.chundru@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mohd.anwar@oss.qualcomm.com \
--cc=monish.chunara@oss.qualcomm.com \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.org \
--cc=umang.chheda@oss.qualcomm.com \
/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