From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Michael Hennerich" <Michael.Hennerich@analog.com>,
"Jean Delvare" <jdelvare@suse.com>,
"Guenter Roeck" <linux@roeck-us.net>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Nuno Sá" <nuno.sa@analog.com>,
"Robert Marko" <robert.marko@sartura.hr>,
"Luka Perkov" <luka.perkov@sartura.hr>,
"Alexandru Tachici" <alexandru.tachici@analog.com>,
"Akshay Gupta" <Akshay.Gupta@amd.com>,
"Kun Yi" <kunyi@google.com>,
"Supreeth Venkatesh" <supreeth.venkatesh@amd.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Eric Tremblay" <etremblay@distech-controls.com>,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Rob Herring <robh@kernel.org>
Subject: [PATCH v2 1/2] dt-bindings: hwmon: adi,ltc2992: correct unit address in example
Date: Wed, 18 Jan 2023 18:22:36 +0100 [thread overview]
Message-ID: <20230118172237.349111-1-krzysztof.kozlowski@linaro.org> (raw)
lower-case hex is expected for unit addresses:
adi,ltc2992.example.dts:22.24-38.15: Warning (i2c_bus_reg): /example-0/i2c/ltc2992@6F: I2C bus unit address format error, expected "6f"
Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Reviewed-by: Rob Herring <robh@kernel.org>
---
Changes since v1:
1. Add Rb tag
2. Reorder patches to silence warnings.
---
Documentation/devicetree/bindings/hwmon/adi,ltc2992.yaml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/hwmon/adi,ltc2992.yaml b/Documentation/devicetree/bindings/hwmon/adi,ltc2992.yaml
index 64a8fcb7bc46..ec984248219e 100644
--- a/Documentation/devicetree/bindings/hwmon/adi,ltc2992.yaml
+++ b/Documentation/devicetree/bindings/hwmon/adi,ltc2992.yaml
@@ -59,12 +59,12 @@ examples:
#address-cells = <1>;
#size-cells = <0>;
- ltc2992@6F {
+ ltc2992@6f {
#address-cells = <1>;
#size-cells = <0>;
compatible = "adi,ltc2992";
- reg = <0x6F>;
+ reg = <0x6f>;
channel@0 {
reg = <0x0>;
--
2.34.1
next reply other threads:[~2023-01-18 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 17:22 Krzysztof Kozlowski [this message]
2023-01-18 17:22 ` [PATCH v2 2/2] dt-bindings: hwmon: correct indentation and style in examples Krzysztof Kozlowski
2023-01-18 18:57 ` Guenter Roeck
2023-01-18 18:57 ` [PATCH v2 1/2] dt-bindings: hwmon: adi,ltc2992: correct unit address in example Guenter Roeck
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=20230118172237.349111-1-krzysztof.kozlowski@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Akshay.Gupta@amd.com \
--cc=Michael.Hennerich@analog.com \
--cc=alexandru.tachici@analog.com \
--cc=devicetree@vger.kernel.org \
--cc=etremblay@distech-controls.com \
--cc=jdelvare@suse.com \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kunyi@google.com \
--cc=linus.walleij@linaro.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=luka.perkov@sartura.hr \
--cc=nuno.sa@analog.com \
--cc=robert.marko@sartura.hr \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=supreeth.venkatesh@amd.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;
as well as URLs for NNTP newsgroup(s).