From: Maxime Ripard <mripard@kernel.org>
To: Ryan Walklin <ryan@testtoast.com>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
Neil Armstrong <neil.armstrong@linaro.org>,
Jessica Zhang <quic_jesszhan@quicinc.com>,
Sam Ravnborg <sam@ravnborg.org>,
David Airlie <airlied@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Hironori KIKUCHI <kikuchan98@gmail.com>,
Chris Morgan <macroalpha82@gmail.com>,
Andre Przywara <andre.przywara@arm.com>,
John Watts <contact@jookia.org>,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v3 1/2] dt-bindings: display: panel: Add WL-355608-A8 panel
Date: Thu, 6 Jun 2024 11:32:16 +0200 [thread overview]
Message-ID: <20240606-intelligent-aromatic-magpie-80a7a4@houat> (raw)
In-Reply-To: <20240530211415.44201-3-ryan@testtoast.com>
[-- Attachment #1: Type: text/plain, Size: 644 bytes --]
On Fri, May 31, 2024 at 09:12:14AM GMT, Ryan Walklin wrote:
> The WL-355608-A8 is a 3.5" 640x480@60Hz RGB LCD display used in a
> number of handheld gaming devices made by Anbernic. By consensus a
> vendor prefix is not provided as the panel OEM is unknown.
Where has this consensus been found?
I had a look at the previous discussions, and I can't find any consensus
being reached there. And for that kind of thing, having the ack or
review of any of the DT maintainers would have been great.
For this kind of cases, we usually use the device it's attached to as
the vendor, so anbernic in this case. Can you send a followup patch?
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]
next prev parent reply other threads:[~2024-06-06 9:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 21:12 [PATCH v3 0/2] Add WL-355608-A8 panel Ryan Walklin
2024-05-30 21:12 ` [PATCH v3 1/2] dt-bindings: display: panel: " Ryan Walklin
2024-06-06 9:32 ` Maxime Ripard [this message]
2024-06-06 9:37 ` Neil Armstrong
2024-06-06 9:48 ` Ryan Walklin
2024-06-06 11:24 ` Maxime Ripard
2024-06-06 11:23 ` Maxime Ripard
2024-06-06 11:51 ` Conor Dooley
2024-06-18 9:04 ` Maxime Ripard
2024-06-18 11:13 ` Conor Dooley
2024-06-18 12:05 ` Neil Armstrong
2024-06-26 8:56 ` Maxime Ripard
2024-06-26 9:10 ` Ryan Walklin
2024-06-26 9:16 ` Neil Armstrong
2024-06-26 11:00 ` Ryan Walklin
2024-06-06 13:49 ` Neil Armstrong
2024-05-30 21:12 ` [PATCH v3 2/2] drm: panel: nv3052c: " Ryan Walklin
2024-06-03 8:39 ` Neil Armstrong
2024-06-03 8:46 ` [PATCH v3 0/2] " 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=20240606-intelligent-aromatic-magpie-80a7a4@houat \
--to=mripard@kernel.org \
--cc=airlied@gmail.com \
--cc=andre.przywara@arm.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=contact@jookia.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kikuchan98@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=macroalpha82@gmail.com \
--cc=neil.armstrong@linaro.org \
--cc=quic_jesszhan@quicinc.com \
--cc=robh@kernel.org \
--cc=ryan@testtoast.com \
--cc=sam@ravnborg.org \
--cc=tzimmermann@suse.de \
/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