From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Sahin, Okan" <Okan.Sahin@analog.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
"open list:VOLTAGE AND CURRENT REGULATOR FRAMEWORK"
<linux-kernel@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 4/5] dt-bindings: regulator: adi,max77541-regulator.yaml Add MAX77541 Regulator bindings
Date: Sun, 15 Jan 2023 20:12:36 +0100 [thread overview]
Message-ID: <72600a64-00a6-fecd-61d9-b93ee83e0fe4@linaro.org> (raw)
In-Reply-To: <MN2PR03MB51688C9858CC8CA7CACCDB22E7C09@MN2PR03MB5168.namprd03.prod.outlook.com>
On 15/01/2023 18:41, Sahin, Okan wrote:
>>> +patternProperties:
>>> + "^BUCK[12]$":
>>
>> Old DT example was correct - lowercase node names.
> Actually, I did not change this part of the patch. I checked other examples, and it looks like using upper case under regulators node seems correct to me. Additionally, there is no warning or error after "make dt_binding_check".
What do you mean "correct"? The convention is simple - all node names
are lowercase. Why this is an exception?
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-01-15 19:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221226223839.103460-1-okan.sahin@analog.com>
2022-12-26 22:38 ` [PATCH v2 1/5] drivers: mfd: Add MAX77541/MAX77540 PMIC Support Okan Sahin
2022-12-26 22:38 ` [PATCH v2 2/5] dt-bindings: mfd: adi,max77541.yaml Add MAX77541 bindings Okan Sahin
2022-12-27 7:53 ` Krzysztof Kozlowski
2023-01-15 17:40 ` Sahin, Okan
2023-01-15 19:16 ` Krzysztof Kozlowski
2022-12-28 0:27 ` Rob Herring
2022-12-26 22:38 ` [PATCH v2 3/5] drivers: regulator: Add MAX77541 Regulator Support Okan Sahin
2022-12-26 22:38 ` [PATCH v2 4/5] dt-bindings: regulator: adi,max77541-regulator.yaml Add MAX77541 Regulator bindings Okan Sahin
2022-12-27 7:56 ` Krzysztof Kozlowski
2023-01-15 17:41 ` Sahin, Okan
2023-01-15 19:12 ` Krzysztof Kozlowski [this message]
2022-12-29 4:49 ` kernel test robot
2022-12-26 22:38 ` [PATCH v2 5/5] drivers: iio: adc: Add MAX77541 ADC Support Okan Sahin
2022-12-30 17:50 ` Jonathan Cameron
2023-01-15 13:03 ` Sahin, Okan
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=72600a64-00a6-fecd-61d9-b93ee83e0fe4@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Okan.Sahin@analog.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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®