From: <Andrei.Simion@microchip.com>
To: <krzysztof.kozlowski@linaro.org>,
<krzysztof.kozlowski+dt@linaro.org>, <robh+dt@kernel.org>,
<conor+dt@kernel.org>, <claudiu.beznea@tuxon.dev>,
<lgirdwood@gmail.com>, <broonie@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2] regulator: dt-bindings: microchip,mcp16502: convert to YAML
Date: Tue, 30 Jan 2024 15:22:54 +0000 [thread overview]
Message-ID: <7fc29a9d-a3ae-44ea-a490-88ecad18983a@microchip.com> (raw)
In-Reply-To: <b749512c-b9c3-4b0e-85e2-cf5114534102@linaro.org>
On 30.01.2024 10:21, Krzysztof Kozlowski wrote:
> [You don't often get email from krzysztof.kozlowski@linaro.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On 29/01/2024 14:53, Andrei Simion wrote:
>> Convert devicetree binding mcp16502-regulator.txt to YAML format.
>>
>> Signed-off-by: Andrei Simion <andrei.simion@microchip.com>
>
> Thank you for your patch. There is something to discuss/improve.
>
>> ---
>> Changes v1 -> v2:
>> - reverse subject prefixes
>> - line break after file "description:"
>> - drop description for reg
>> - drop regulator-name
>> - add regulator-initial-mode
>> - unevaluatedProperties just after $ref: regulator.yaml#
>> - additionalProperties just before "required"
>> - node names generic in example
>> - use 4 spaces for example indentation
>
>
>> +
>> + reg:
>> + maxItems: 1
>> +
>> + regulators:
>> + type: object
additionalProperties: false -> forgot this line. That is my missing to hit all the points in the previous review. Let me know If that is all.
>> + description: List of regulators and its properties.
>> + A node that houses a sub-node for each regulator within
>> + the device. Each sub-node is identified using the node's
>> + name. The content of each sub-node is defined by the
>> + standard binding for regulators;>
> This is a friendly reminder during the review process.
>
> It seems my or other reviewer's previous comments were not fully
> addressed. Maybe the feedback got lost between the quotes, maybe you
> just forgot to apply it. Please go back to the previous discussion and
> either implement all requested changes or keep discussing them.
> > Also: you can keep just one line of description. Rest is redundant.
>
Yes, I will change in v3 .
>> Best regards,
> Krzysztof
>
Thank you for review and best regards,
Andrei Simion
next prev parent reply other threads:[~2024-01-30 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 13:53 [PATCH v2] regulator: dt-bindings: microchip,mcp16502: convert to YAML Andrei Simion
2024-01-30 8:21 ` Krzysztof Kozlowski
2024-01-30 15:22 ` Andrei.Simion [this message]
2024-01-30 16:16 ` Krzysztof Kozlowski
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=7fc29a9d-a3ae-44ea-a490-88ecad18983a@microchip.com \
--to=andrei.simion@microchip.com \
--cc=broonie@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).