From: Sam Ravnborg <sam@ravnborg.org>
To: Adam Ford <aford173@gmail.com>
Cc: dri-devel@lists.freedesktop.org, linux-omap@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V5 2/3] dt-bindings: Add Logic PD Type 28 display panel
Date: Sat, 30 Nov 2019 23:15:33 +0100 [thread overview]
Message-ID: <20191130221533.GC29715@ravnborg.org> (raw)
In-Reply-To: <20191016135147.7743-2-aford173@gmail.com>
Hi Adam.
On Wed, Oct 16, 2019 at 08:51:46AM -0500, Adam Ford wrote:
> This patch adds documentation of device tree bindings for the WVGA panel
> Logic PD Type 28 display.
>
> Signed-off-by: Adam Ford <aford173@gmail.com>
> ---
> V5: Replace GPIO_ACTIVE_HIGH with 0 to fix make dt_binding_check -k
> V4: Update per Rob H's suggestions and copy other panel yaml example from 5.4-rc1
> V3: Correct build errors from 'make dt_binding_check'
> V2: Use YAML instead of TXT for binding
>
Applied to drm-misc-next.
It was applied before the driver changes so we had bindings
for the driver changes when applied.
Sam
next prev parent reply other threads:[~2019-11-30 22:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191016135147.7743-1-aford173@gmail.com>
[not found] ` <20191016135147.7743-3-aford173@gmail.com>
2019-10-21 17:19 ` [PATCH V5 3/3] ARM: logicpd-torpedo-37xx-devkit-28: Reference new DRM panel Tony Lindgren
2019-10-30 14:44 ` [PATCH V5 1/3] drm/panel: simple: Add Logic PD Type 28 display support Adam Ford
2019-11-01 7:57 ` Laurent Pinchart
2019-11-11 13:19 ` Adam Ford
2019-11-24 11:17 ` Adam Ford
[not found] ` <20191016135147.7743-2-aford173@gmail.com>
2019-11-30 22:15 ` Sam Ravnborg [this message]
2019-11-30 22:16 ` Sam Ravnborg
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=20191130221533.GC29715@ravnborg.org \
--to=sam@ravnborg.org \
--cc=aford173@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=thierry.reding@gmail.com \
--cc=tomi.valkeinen@ti.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).