From: sashiko-bot@kernel.org
To: "Neil Armstrong" <neil.armstrong@linaro.org>
Cc: devicetree@vger.kernel.org, linux-hwmon@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v5 1/3] dt-bindings: iio: add: document the MAX34417 Four-Channel High Dynamic Range Power Accumulator
Date: Mon, 02 Nov 2026 14:56:02 +0000 [thread overview]
Message-ID: <sashiko-outbox-193619@kernel.org> (raw)
In-Reply-To: <20261102-topic-sm8x50-iio-max34417-adc-v5-1-0ffa5e5f2d5c@linaro.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: iio: adc: adi,max34417: inconsistent indentation in DTS example
--
commit a9428a6f2a12de2abe990a839ca0d1e5820c2ceb
Author: Neil Armstrong <neil.armstrong@linaro.org>
dt-bindings: iio: add: document the MAX34417 Four-Channel High Dynamic Range Power Accumulator
This patch adds a Device Tree binding schema for the Analog Devices
MAX34417 Four-Channel High Dynamic Range Power Accumulator.
> diff --git a/Documentation/devicetree/bindings/iio/adc/adi,max34417.yaml b/Documentation/devicetree/bindings/iio/adc/adi,max34417.yaml
> new file mode 100644
> index 0000000000000..700bc3ca7d7cf
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/adc/adi,max34417.yaml
> @@ -0,0 +1,103 @@
[ ... ]
> +examples:
> + - |
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + sensor@10 {
> + compatible = "adi,max34417";
> + reg = <0x10>;
> +
> + vdd-supply = <&max34417_vdd>;
> + vio-supply = <&max34417_vio>;
> +
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + channel@0 {
> + reg = <0>;
> + label = "ch0";
> + shunt-resistor-micro-ohms = <5000>;
> + };
> +
> + channel@1 {
> + reg = <1>;
> + label = "ch1";
> + };
> +
> + channel@2 {
> + reg = <2>;
> + };
> + };
> + };
[Severity: Low]
As reported by Krzysztof Kozlowski on v2 [1], the DTS example in
Documentation/devicetree/bindings/iio/adc/adi,max34417.yaml has inconsistent
indentation that fails scripts/dtc/dt-check-style --mode strict.
Inside sensor@10, the properties and child channel nodes are indented by 6
spaces relative to sensor@10 instead of 4 spaces, and the closing braces for
channel@1 and channel@2 are misaligned by one space relative to their opening
lines.
Should the example use consistent 4-space indentation throughout sensor@10 and
its child channel nodes?
[1] https://lore.kernel.org/r/20260929-heavy-intelligent-guillemot-da269b@quoll
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261102-topic-sm8x50-iio-max34417-adc-v5-0-0ffa5e5f2d5c@linaro.org?part=1
next prev parent reply other threads:[~2026-11-02 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 14:49 [PATCH v5 0/3] iio: adc: add support for the MAX34417 Four-Channel High Dynamic Range Power Accumulator Neil Armstrong
2026-11-02 14:49 ` [PATCH v5 1/3] dt-bindings: iio: add: document " Neil Armstrong
2026-11-02 14:56 ` sashiko-bot [this message]
2026-11-02 14:49 ` [PATCH v5 2/3] unaligned: introduce be56 unaligned accessors Neil Armstrong
2026-11-02 14:49 ` [PATCH v5 3/3] iio: adc: add driver for the MAX34417 Four-Channel High Dynamic Range Power Accumulator Neil Armstrong
2026-11-02 15:11 ` sashiko-bot
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=sashiko-outbox-193619@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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