linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Daniel Vetter <daniel@ffwll.ch>, Rob Clark <robdclark@gmail.com>,
	devicetree@vger.kernel.org, David Airlie <airlied@linux.ie>,
	linux-kernel@vger.kernel.org, Sean Paul <sean@poorly.run>,
	Marek Vasut <marex@denx.de>,
	dri-devel@lists.freedesktop.org,
	Krishna Manikandan <mkrishn@codeaurora.org>
Subject: Re: [PATCH] dt-bindings: display: Fix graph 'unevaluatedProperties' related warnings
Date: Fri, 23 Jul 2021 15:17:48 -0600	[thread overview]
Message-ID: <20210723211748.GA2601003@robh.at.kernel.org> (raw)
In-Reply-To: <20210719195001.2412345-1-robh@kernel.org>

On Mon, 19 Jul 2021 13:50:01 -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: David Airlie <airlied@linux.ie>
> Cc: Daniel Vetter <daniel@ffwll.ch>
> Cc: Rob Clark <robdclark@gmail.com>
> Cc: Sean Paul <sean@poorly.run>
> Cc: Marek Vasut <marex@denx.de>
> Cc: Krishna Manikandan <mkrishn@codeaurora.org>
> Cc: dri-devel@lists.freedesktop.org
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
>  .../devicetree/bindings/display/bridge/ti,sn65dsi83.yaml    | 6 ++++--
>  .../bindings/display/msm/dsi-controller-main.yaml           | 6 ++++--
>  2 files changed, 8 insertions(+), 4 deletions(-)
> 

Applied, thanks!

  reply	other threads:[~2021-07-23 21:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19 19:50 [PATCH] dt-bindings: display: Fix graph 'unevaluatedProperties' related warnings Rob Herring
2021-07-23 21:17 ` Rob Herring [this message]
     [not found] ` <YPXZODWTE3qHQqEv@ravnborg.org>
2021-07-23 21:25   ` Rob Herring

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=20210723211748.GA2601003@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=mkrishn@codeaurora.org \
    --cc=robdclark@gmail.com \
    --cc=sean@poorly.run \
    /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).