From: Rob Herring <robh@kernel.org>
To: Fabrizio Castro <fabrizio.castro.jz@renesas.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Chris Paterson <Chris.Paterson2@renesas.com>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-media@vger.kernel.org,
Biju Das <biju.das.jz@bp.renesas.com>,
Ramesh Shanmugasundaram <rashanmu@gmail.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [PATCH] media: dt-bindings: media: renesas,drif: Fix fck definition
Date: Tue, 8 Jun 2021 20:04:16 -0500 [thread overview]
Message-ID: <20210609010416.GA2010770@robh.at.kernel.org> (raw)
In-Reply-To: <20210408202436.3706-1-fabrizio.castro.jz@renesas.com>
On Thu, 08 Apr 2021 21:24:36 +0100, Fabrizio Castro wrote:
> dt_binding_check reports the below error with the latest schema:
>
> Documentation/devicetree/bindings/media/renesas,drif.yaml:
> properties:clock-names:maxItems: False schema does not allow 1
> Documentation/devicetree/bindings/media/renesas,drif.yaml:
> ignoring, error in schema: properties: clock-names: maxItems
>
> This patch fixes the problem.
>
> Signed-off-by: Fabrizio Castro <fabrizio.castro.jz@renesas.com>
> ---
> Documentation/devicetree/bindings/media/renesas,drif.yaml | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
Applied, thanks!
prev parent reply other threads:[~2021-06-09 1:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 20:24 [PATCH] media: dt-bindings: media: renesas,drif: Fix fck definition Fabrizio Castro
2021-04-09 18:54 ` Rob Herring
2021-04-27 18:02 ` Rob Herring
2021-04-27 20:08 ` Laurent Pinchart
2021-06-04 19:38 ` Rob Herring
2021-06-04 22:05 ` Laurent Pinchart
2021-06-09 1:04 ` Rob Herring [this message]
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=20210609010416.GA2010770@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--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).