From: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
To: Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
"Ramesh Shanmugasundaram" <rashanmu@gmail.com>,
linux-media <linux-media@vger.kernel.org>,
linux-renesas-soc <linux-renesas-soc@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>
Subject: Re: [PATCH 1/1] media: dt-bindings: media: renesas,drif: Fix a dt_binding_check warning
Date: Fri, 4 Jun 2021 11:15:49 +0800 [thread overview]
Message-ID: <a9522c05-a0d7-4017-f42b-a8e4b2a8c0e2@huawei.com> (raw)
In-Reply-To: <20210520114953.8206-1-thunder.leizhen@huawei.com>
Hi all:
Can someone review this patch?
On 2021/5/20 19:49, Zhen Lei wrote:
> The value of the property 'clock-names' is a constant string, so the
> 'maxItems: 1' is not needed, should be removed. Otherwise, the following
> warning is reported:
> properties:clock-names:maxItems: False schema does not allow 1
> ignoring, error in schema: properties: clock-names: maxItems
> warning: no schema found in file: xxx/bindings/media/renesas,drif.yaml
>
> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
> ---
> Documentation/devicetree/bindings/media/renesas,drif.yaml | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/media/renesas,drif.yaml b/Documentation/devicetree/bindings/media/renesas,drif.yaml
> index f1bdaeab4053..b7f07062922f 100644
> --- a/Documentation/devicetree/bindings/media/renesas,drif.yaml
> +++ b/Documentation/devicetree/bindings/media/renesas,drif.yaml
> @@ -67,7 +67,6 @@ properties:
> maxItems: 1
>
> clock-names:
> - maxItems: 1
> items:
> - const: fck
>
>
next prev parent reply other threads:[~2021-06-04 3:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 11:49 [PATCH 1/1] media: dt-bindings: media: renesas,drif: Fix a dt_binding_check warning Zhen Lei
2021-06-04 3:15 ` Leizhen (ThunderTown) [this message]
2021-06-04 8:54 ` Fabrizio Castro
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=a9522c05-a0d7-4017-f42b-a8e4b2a8c0e2@huawei.com \
--to=thunder.leizhen@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrizio.castro.jz@renesas.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rashanmu@gmail.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).