From: Sam Ravnborg <sam@ravnborg.org>
To: Marek Vasut <marex@denx.de>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
Sean Cross <xobs@kosagi.com>, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH 2/3] dt-bindings: it6251: add bindings for IT6251 LVDS-to-eDP bridge
Date: Sun, 2 Feb 2020 19:23:46 +0100 [thread overview]
Message-ID: <20200202182346.GA18495@ravnborg.org> (raw)
In-Reply-To: <20200127022023.379080-2-marex@denx.de>
Hi Marek.
On Mon, Jan 27, 2020 at 03:20:22AM +0100, Marek Vasut wrote:
> Add DT bindings for ITE IT6251 LVDS-to-eDP bridge.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> Cc: Daniel Vetter <daniel@ffwll.ch>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Sean Cross <xobs@kosagi.com>
> Cc: devicetree@vger.kernel.org
> To: dri-devel@lists.freedesktop.org
> ---
> .../bindings/display/bridge/ite,it6251.txt | 35 +++++++++++++++++++
Any chance you could make this follow the DT Schema (.yaml) syntax
so we get better verification of the DT files?
Sam
next prev parent reply other threads:[~2020-02-02 18:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 2:20 [PATCH 1/3] dt-bindings: Add ITE Tech prefix Marek Vasut
2020-01-27 2:20 ` [PATCH 2/3] dt-bindings: it6251: add bindings for IT6251 LVDS-to-eDP bridge Marek Vasut
2020-02-02 18:23 ` Sam Ravnborg [this message]
2020-02-10 9:09 ` Neil Armstrong
2020-02-03 15:53 ` [PATCH 1/3] dt-bindings: Add ITE Tech prefix Rob Herring
-- strict thread matches above, loose matches on Subject: below --
2016-10-17 16:33 Marek Vasut
[not found] ` <20161017163329.11821-1-marex-ynQEQJNshbs@public.gmane.org>
2016-10-17 16:33 ` [PATCH 2/3] dt-bindings: it6251: add bindings for IT6251 LVDS-to-eDP bridge Marek Vasut
[not found] ` <20161017163329.11821-2-marex-ynQEQJNshbs@public.gmane.org>
2016-10-18 16:30 ` Rob Herring
2016-10-18 16:35 ` Marek Vasut
2016-10-18 19:58 ` 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=20200202182346.GA18495@ravnborg.org \
--to=sam@ravnborg.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=marex@denx.de \
--cc=robh+dt@kernel.org \
--cc=xobs@kosagi.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).