From: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
linux-serial@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Subject: [PATCH v2 1/2] dt-bindings: serial: uniphier: Use maxItems for a single clock
Date: Wed, 30 Mar 2022 14:15:37 +0900 [thread overview]
Message-ID: <1648617338-8600-2-git-send-email-hayashi.kunihiko@socionext.com> (raw)
In-Reply-To: <1648617338-8600-1-git-send-email-hayashi.kunihiko@socionext.com>
'maxItems' is preferred for a single entry, not 'minItems'.
Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
---
.../devicetree/bindings/serial/socionext,uniphier-uart.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/serial/socionext,uniphier-uart.yaml b/Documentation/devicetree/bindings/serial/socionext,uniphier-uart.yaml
index d490c7c4b967..06353028b274 100644
--- a/Documentation/devicetree/bindings/serial/socionext,uniphier-uart.yaml
+++ b/Documentation/devicetree/bindings/serial/socionext,uniphier-uart.yaml
@@ -20,7 +20,7 @@ properties:
maxItems: 1
clocks:
- minItems: 1
+ maxItems: 1
auto-flow-control:
description: enable automatic flow control support.
--
2.25.1
next prev parent reply other threads:[~2022-03-30 5:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 5:15 [PATCH v2 0/2] dt-bindings: serial: uniphier: Fix clocks and resets properties Kunihiko Hayashi
2022-03-30 5:15 ` Kunihiko Hayashi [this message]
2022-03-30 8:16 ` [PATCH v2 1/2] dt-bindings: serial: uniphier: Use maxItems for a single clock Krzysztof Kozlowski
2022-03-30 5:15 ` [PATCH v2 2/2] dt-bindings: serial: uniphier: Add "resets" property as optional Kunihiko Hayashi
2022-03-30 8:16 ` Krzysztof Kozlowski
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=1648617338-8600-2-git-send-email-hayashi.kunihiko@socionext.com \
--to=hayashi.kunihiko@socionext.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mhiramat@kernel.org \
--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
all inboxes | Powered by JetHome®