From: Conor Dooley <conor@kernel.org>
To: Marek Vasut <marex@denx.de>
Cc: dri-devel@lists.freedesktop.org,
Conor Dooley <conor+dt@kernel.org>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Sam Ravnborg <sam@ravnborg.org>,
Thierry Reding <thierry.reding@gmail.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: display: simple: Add Innolux G156HCE-L01 panel
Date: Tue, 1 Aug 2023 16:42:15 +0100 [thread overview]
Message-ID: <20230801-apostle-blurt-db4683b4cf95@spud> (raw)
In-Reply-To: <20230731210258.256152-1-marex@denx.de>
[-- Attachment #1: Type: text/plain, Size: 468 bytes --]
On Mon, Jul 31, 2023 at 11:02:57PM +0200, Marek Vasut wrote:
> Add entry for Innolux G156HCE-L01 15.6" 1920x1080 24bpp
> dual-link LVDS TFT panel. Documentation is available at [1].
>
> [1] https://www.distec.de/fileadmin/pdf/produkte/TFT-Displays/Innolux/G156HCE-L01_Rev.C3_Datasheet.pdf
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> ---
> Cc: Conor Dooley <conor+dt@kernel.org>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
Thanks,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-08-01 15:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 21:02 [PATCH 1/2] dt-bindings: display: simple: Add Innolux G156HCE-L01 panel Marek Vasut
2023-07-31 21:02 ` [PATCH 2/2] drm/panel-simple: Add Innolux G156HCE-L01 panel entry Marek Vasut
2023-08-03 8:24 ` Neil Armstrong
2023-08-03 14:23 ` Luca Ceresoli
2023-08-03 14:25 ` Marek Vasut
2023-08-03 15:06 ` Luca Ceresoli
2023-08-03 17:10 ` Marek Vasut
2023-08-04 8:19 ` Luca Ceresoli
2023-08-04 14:30 ` Luca Ceresoli
2023-08-01 15:42 ` Conor Dooley [this message]
2023-08-03 8:27 ` [PATCH 1/2] dt-bindings: display: simple: Add Innolux G156HCE-L01 panel Neil Armstrong
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=20230801-apostle-blurt-db4683b4cf95@spud \
--to=conor@kernel.org \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=marex@denx.de \
--cc=neil.armstrong@linaro.org \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=thierry.reding@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).