From: Lars-Peter Clausen <lars@metafoo.de>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Michal Simek <michal.simek@amd.com>,
devicetree@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>
Subject: [PATCH 1/2] dt-bindings: i2c: xiic: Fix `clock-names` property name
Date: Sat, 18 Mar 2023 06:42:54 -0700 [thread overview]
Message-ID: <20230318134255.282359-1-lars@metafoo.de> (raw)
The Xilinx I2C controller device tree bindings documentation documents a
`clock-name` property. There is no such property, the correct property name
is `clock-names` with a `s`. The `s` was accidentally dropped during
conversion from txt to yaml.
Fixes: f86ca4147976 ("dt-bindings: i2c: xiic: Migrate i2c-xiic documentation to YAML")
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
---
Documentation/devicetree/bindings/i2c/xlnx,xps-iic-2.00.a.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/i2c/xlnx,xps-iic-2.00.a.yaml b/Documentation/devicetree/bindings/i2c/xlnx,xps-iic-2.00.a.yaml
index 1b598638d457..cc40a61a1c8e 100644
--- a/Documentation/devicetree/bindings/i2c/xlnx,xps-iic-2.00.a.yaml
+++ b/Documentation/devicetree/bindings/i2c/xlnx,xps-iic-2.00.a.yaml
@@ -27,7 +27,7 @@ properties:
clocks:
minItems: 1
- clock-name:
+ clock-names:
const: pclk
description: |
Input clock name.
--
2.30.2
next reply other threads:[~2023-03-18 13:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-18 13:42 Lars-Peter Clausen [this message]
2023-03-18 13:42 ` [PATCH 2/2] dt-bindings: i2c: cadence: Fix `clock-names` property name Lars-Peter Clausen
2023-03-19 12:03 ` Krzysztof Kozlowski
2023-03-20 7:36 ` Michal Simek
2023-03-19 12:03 ` [PATCH 1/2] dt-bindings: i2c: xiic: " Krzysztof Kozlowski
2023-03-20 7:36 ` Michal Simek
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=20230318134255.282359-1-lars@metafoo.de \
--to=lars@metafoo.de \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=michal.simek@amd.com \
--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).