From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Wolfram Sang <wsa@the-dreams.de>,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Gregory Clement <gregory.clement@bootlin.com>
Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
Maxime Ripard <maxime.ripard@bootlin.com>
Subject: [PATCH 1/2] dt-bindings: i2c: mv64xxx: Fix the example compatible
Date: Wed, 3 Jul 2019 11:53:37 +0200 [thread overview]
Message-ID: <20190703095338.11266-1-maxime.ripard@bootlin.com> (raw)
One example has a compatible that isn't a valid combination according to
the binding, and now that the examples are validated as well, this
generates a warning.
Let's fix this.
Signed-off-by: Maxime Ripard <maxime.ripard@bootlin.com>
---
Documentation/devicetree/bindings/i2c/marvell,mv64xxx-i2c.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/i2c/marvell,mv64xxx-i2c.yaml b/Documentation/devicetree/bindings/i2c/marvell,mv64xxx-i2c.yaml
index 9a5654ef5670..001f2b7abad0 100644
--- a/Documentation/devicetree/bindings/i2c/marvell,mv64xxx-i2c.yaml
+++ b/Documentation/devicetree/bindings/i2c/marvell,mv64xxx-i2c.yaml
@@ -105,7 +105,7 @@ examples:
- |
i2c@11000 {
- compatible = "marvell,mv78230-i2c", "marvell,mv64xxx-i2c";
+ compatible = "marvell,mv78230-i2c";
reg = <0x11000 0x100>;
interrupts = <29>;
clock-frequency = <100000>;
--
2.21.0
next reply other threads:[~2019-07-03 9:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 9:53 Maxime Ripard [this message]
2019-07-03 9:53 ` [PATCH 2/2] dt-bindings: i2c: sun6i-p2wi: Fix the binding example Maxime Ripard
2019-07-05 10:34 ` Gregory CLEMENT
2019-07-05 16:21 ` Rob Herring
2019-07-05 18:33 ` Wolfram Sang
2019-07-05 10:34 ` [PATCH 1/2] dt-bindings: i2c: mv64xxx: Fix the example compatible Gregory CLEMENT
2019-07-05 16:22 ` Rob Herring
2019-07-05 18:32 ` Wolfram Sang
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=20190703095338.11266-1-maxime.ripard@bootlin.com \
--to=maxime.ripard@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=gregory.clement@bootlin.com \
--cc=linux-i2c@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=wsa@the-dreams.de \
/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).