devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Bhavin Sharma <bhavin.sharma@siliconsignals.io>,
	sre@kernel.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org
Cc: Hardevsinh Palaniya <hardevsinh.palaniya@siliconsignals.io>,
	linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] dt-bindings: power: supply: st,stc3117
Date: Mon, 5 Feb 2024 08:48:31 +0100	[thread overview]
Message-ID: <e7ac77fe-b722-4b88-911c-c8300776370e@linaro.org> (raw)
In-Reply-To: <20240205051321.4079933-2-bhavin.sharma@siliconsignals.io>

On 05/02/2024 06:13, Bhavin Sharma wrote:
> Signed-off-by: Bhavin Sharma <bhavin.sharma@siliconsignals.io>

You cannot have empty commits.

Subject: It's empty? What happened there?

> ---
> Changelogs :
> 
> v2 -> v3
> - Resolved DTC warnings and errors
> - Formatted the changelogs
> - Added monitored battery properties
> - Replaced 'additionalProperties' with 'unevaluatedProperties'
> - Replaced '&i2c6' with 'i2c'
> 
> v1 -> v2
> - String value is redundantly quoted with any quotes (quoted-strings)
> - Found character '\t' that cannot start any token
> ---

Please run scripts/checkpatch.pl and fix reported warnings. Some
warnings can be ignored, but the code here looks like it needs a fix.
Feel free to get in touch if the warning is not clear.

>  .../bindings/power/supply/st,stc3117.yaml     | 49 +++++++++++++++++++
>  1 file changed, 49 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/power/supply/st,stc3117.yaml
> 
> diff --git a/Documentation/devicetree/bindings/power/supply/st,stc3117.yaml b/Documentation/devicetree/bindings/power/supply/st,stc3117.yaml
> new file mode 100644
> index 000000000000..9ab0b0d6b30e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/power/supply/st,stc3117.yaml
> @@ -0,0 +1,49 @@
> +# SPDX-License-Identifier: GPL-2.0-only

Dual license, just like checkpatch asks.

> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/power/supply/st,stc3117.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: STMicroelectronics STC3117 Fuel Gauge Unit Power Supply
> +
> +maintainers:
> +  - Bhavin Sharma <bhavin.sharma@siliconsignals.io>
> +  - Hardevsinh Palaniya <hardevsinh.palaniya@siliconsignals.io>
> +
> +allOf:
> +  - $ref: power-supply.yaml#
> +
> +properties:
> +  compatible:
> +    enum:
> +      - st,stc3117
> +
> +  reg:
> +    maxItems: 1

Are you going to answer my questions or just ignore them?

> +
> +required:
> +  - compatible
> +  - reg
> +
> +unevaluatedProperties: false
> +
> +examples:
> +  - |
> +    bat: battery {

Drop node


> +       compatible = "simple-battery";
> +       device-chemistry = "lithium-ion-polymer";
> +       energy-full-design-microwatt-hours = <16800000>;
> +       charge-full-design-microamp-hours = <4000000>;
> +       voltage-min-design-microvolt = <3000000>;
> +    };
> +
> +    i2c {
> +      #address-cells = <1>;
> +      #size-cells = <0>;
> +
> +      stc3117@70 {

Still wrong name.

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.

Thank you.


Best regards,
Krzysztof


  reply	other threads:[~2024-02-05  7:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05  5:13 [PATCH v3 1/2] power: supply: Add STC3117 fuel gauge unit driver Bhavin Sharma
2024-02-05  5:13 ` [PATCH v3 2/2] dt-bindings: power: supply: st,stc3117 Bhavin Sharma
2024-02-05  7:48   ` Krzysztof Kozlowski [this message]
2024-02-09 12:41 ` [PATCH v3 1/2] power: supply: Add STC3117 fuel gauge unit driver Bhavin Sharma
2024-02-12  0:14 ` Sebastian Reichel
2024-02-16 13:34   ` Bhavin Sharma
2024-02-16 23:07     ` Sebastian Reichel

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=e7ac77fe-b722-4b88-911c-c8300776370e@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=bhavin.sharma@siliconsignals.io \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hardevsinh.palaniya@siliconsignals.io \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sre@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).