From: Rob Herring <robh@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Ludovic Desroches <ludovic.desroches@microchip.com>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
linux-media@vger.kernel.org,
Eugen Hristev <eugen.hristev@microchip.com>,
Ramesh Shanmugasundaram <rashanmu@gmail.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: media: Fix graph 'unevaluatedProperties' related warnings
Date: Fri, 23 Jul 2021 15:17:37 -0600 [thread overview]
Message-ID: <20210723211737.GA2599616@robh.at.kernel.org> (raw)
In-Reply-To: <20210719194850.2410511-1-robh@kernel.org>
On Mon, 19 Jul 2021 13:48:50 -0600, Rob Herring wrote:
> The graph schema doesn't allow custom properties on endpoint nodes for
> '#/properties/port' and '#/$defs/port-base' should be used instead. This
> doesn't matter until 'unevaluatedProperties' support is implemented.
>
> Cc: Eugen Hristev <eugen.hristev@microchip.com>
> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
> Cc: Nicolas Ferre <nicolas.ferre@microchip.com>
> Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>
> Cc: Ludovic Desroches <ludovic.desroches@microchip.com>
> Cc: Fabrizio Castro <fabrizio.castro.jz@renesas.com>
> Cc: Ramesh Shanmugasundaram <rashanmu@gmail.com>
> Cc: linux-media@vger.kernel.org
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> Documentation/devicetree/bindings/media/atmel,isc.yaml | 3 ++-
> Documentation/devicetree/bindings/media/microchip,xisc.yaml | 2 +-
> Documentation/devicetree/bindings/media/renesas,drif.yaml | 2 +-
> 3 files changed, 4 insertions(+), 3 deletions(-)
>
Applied, thanks!
prev parent reply other threads:[~2021-07-23 21:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 19:48 [PATCH] dt-bindings: media: Fix graph 'unevaluatedProperties' related warnings Rob Herring
2021-07-23 21:17 ` 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=20210723211737.GA2599616@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=eugen.hristev@microchip.com \
--cc=fabrizio.castro.jz@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=mchehab@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=rashanmu@gmail.com \
/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).