From: Rob Herring <robh@kernel.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: devicetree@vger.kernel.org, Marek Vasut <marex@denx.de>,
Krishna Manikandan <mkrishn@codeaurora.org>,
David Airlie <airlied@linux.ie>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Sean Paul <sean@poorly.run>
Subject: Re: [PATCH] dt-bindings: display: Fix graph 'unevaluatedProperties' related warnings
Date: Fri, 23 Jul 2021 15:25:45 -0600 [thread overview]
Message-ID: <CAL_JsqJt=ifqBuvpAXkd5hXb=1tg16a4Sjcq+WuvsinccPuvuQ@mail.gmail.com> (raw)
In-Reply-To: <YPXZODWTE3qHQqEv@ravnborg.org>
On Mon, Jul 19, 2021 at 1:57 PM Sam Ravnborg <sam@ravnborg.org> wrote:
>
> Hi Rob,
> On Mon, Jul 19, 2021 at 01:50:01PM -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>
> Acked-by: Sam Ravnborg <sam@ravnborg.org>
Thanks. FYI, your mail only went thru on dri-devel, but not DT or LKML lists.
Rob
prev parent reply other threads:[~2021-07-23 21:26 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
[not found] ` <YPXZODWTE3qHQqEv@ravnborg.org>
2021-07-23 21:25 ` 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='CAL_JsqJt=ifqBuvpAXkd5hXb=1tg16a4Sjcq+WuvsinccPuvuQ@mail.gmail.com' \
--to=robh@kernel.org \
--cc=airlied@linux.ie \
--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=sam@ravnborg.org \
--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).