From: Rob Herring <robh@kernel.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: dri-devel@lists.freedesktop.org, thierry.reding@gmail.com,
sam@ravnborg.org, robh+dt@kernel.org, devicetree@vger.kernel.org,
mark.rutland@arm.com, christoph.muellner@theobroma-systems.com,
robin.murphy@arm.com, linux-rockchip@lists.infradead.org,
heiko@sntech.de, francescolavra.fl@gmail.com,
Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
Subject: Re: [PATCH v3 1/3] dt-bindings: Add vendor prefix for Elida
Date: Wed, 4 Mar 2020 10:34:26 -0600 [thread overview]
Message-ID: <20200304163426.GA20664@bogus> (raw)
In-Reply-To: <20200229151506.750242-1-heiko@sntech.de>
On Sat, 29 Feb 2020 16:15:04 +0100, Heiko Stuebner wrote:
> From: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
>
> Shenzen Elida Technology Co. Ltd. is a Chinese TFT manufacturer.
>
> Signed-off-by: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
> Acked-by: Sam Ravnborg <sam@ravnborg.org>
> ---
> Hi Rob,
>
> as can be seen on [0], Sam expects you to apply the vendor prefix
> to the main dt-tree.
>
> Thanks
> Heiko
>
> [0] http://lore.kernel.org/r/20200229125725.GC5447@ravnborg.org
>
> Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
Applied, thanks.
Rob
prev parent reply other threads:[~2020-03-04 16:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-29 15:15 [PATCH v3 1/3] dt-bindings: Add vendor prefix for Elida Heiko Stuebner
2020-02-29 15:15 ` [PATCH v3 2/3] dt-bindings: display: panel: Add binding document for Elida KD35T133 Heiko Stuebner
2020-03-04 16:35 ` Rob Herring
2020-03-06 1:41 ` Heiko Stuebner
2020-02-29 15:15 ` [PATCH v3 3/3] drm/panel: add panel driver for Elida KD35T133 panels Heiko Stuebner
2020-03-06 1:41 ` Heiko Stuebner
2020-02-29 15:59 ` [PATCH v3 1/3] dt-bindings: Add vendor prefix for Elida Sam Ravnborg
2020-03-04 16:34 ` 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=20200304163426.GA20664@bogus \
--to=robh@kernel.org \
--cc=christoph.muellner@theobroma-systems.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=francescolavra.fl@gmail.com \
--cc=heiko.stuebner@theobroma-systems.com \
--cc=heiko@sntech.de \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--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).