From: Rob Herring <robh@kernel.org>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
dri-devel@lists.freedesktop.org, robh+dt@kernel.org,
thierry.reding@gmail.com, kernel@pengutronix.de
Subject: Re: [PATCH 1/3] dt-bindings: add vendor prefix for Evervision Electronics
Date: Fri, 11 Jan 2019 11:01:23 -0600 [thread overview]
Message-ID: <20190111170123.GA2431@bogus> (raw)
In-Reply-To: <20190103182658.16377-2-m.felsch@pengutronix.de>
On Thu, 3 Jan 2019 19:26:56 +0100, Marco Felsch wrote:
> Evervision Electronics is a panel manufacturer from Taipei.
> http://www.evervisionlcd.com/index.php?lang=en
>
> Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
> ---
> Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-01-11 17:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 18:26 [PATCH 0/3] drm/panel: simple: Add support for Evervision VGG804821 Marco Felsch
2019-01-03 18:26 ` [PATCH 1/3] dt-bindings: add vendor prefix for Evervision Electronics Marco Felsch
2019-01-11 17:01 ` Rob Herring [this message]
2019-01-03 18:26 ` [PATCH 2/3] dt-bindings: drm/panel: simple: add Evervision VGG804821 Marco Felsch
2019-01-04 16:38 ` Sam Ravnborg
2019-01-11 17:01 ` Rob Herring
2019-01-11 17:17 ` Sam Ravnborg
2019-01-11 17:01 ` Rob Herring
2019-01-03 18:26 ` [PATCH 3/3] drm/panel: simple: Add Evervision VGG804821 pannel support Marco Felsch
2019-01-04 16:40 ` Sam Ravnborg
2019-01-14 10:28 ` Marco Felsch
2019-04-15 15:46 ` Marco Felsch
2019-04-15 16:10 ` Sam Ravnborg
2019-04-15 16:59 ` Marco Felsch
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=20190111170123.GA2431@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@pengutronix.de \
--cc=m.felsch@pengutronix.de \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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).