From: Rob Herring <robh@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Ryan Pannell <ryan@osukl.com>,
devicetree@vger.kernel.org, David Airlie <airlied@linux.ie>,
linux-amarula@amarulasolutions.com, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Thierry Reding <thierry.reding@gmail.com>,
Jagan Teki <jagan@amarulasolutions.com>,
Michael Trimarchi <michael@amarulasolutions.com>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH v2 1/4] dt-bindings: Add vendor prefix for novatek
Date: Sun, 31 Mar 2019 01:41:07 -0500 [thread overview]
Message-ID: <5ca06105.1c69fb81.8e827.7f26@mx.google.com> (raw)
In-Reply-To: <20190321135955.25661-2-jagan@amarulasolutions.com>
On Thu, 21 Mar 2019 19:29:52 +0530, Jagan Teki wrote:
> Add vendor prefix for novatek.
>
> Novatek Microelectronics Corp. is a leading fabless chip design
> company specializing in the design, development and sales of a
> wide range of display driver ICs & SoC solutions.
>
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
> ---
> 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-03-31 6:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 13:59 [PATCH v2 0/4] drm/panel: Add Novatek NT35596 panel Jagan Teki
2019-03-21 13:59 ` [PATCH v2 1/4] dt-bindings: Add vendor prefix for novatek Jagan Teki
2019-03-31 6:41 ` Rob Herring [this message]
2019-03-21 13:59 ` [PATCH v2 2/4] dt-bindings: Add vendor prefix for microtech Jagan Teki
2019-03-31 6:41 ` Rob Herring
2019-03-21 13:59 ` [PATCH v2 3/4] dt-bindings: display: Add Novatek NT35596 panel documentation Jagan Teki
2019-03-31 6:41 ` Rob Herring
2019-03-21 13:59 ` [PATCH v2 4/4] drm/panel: Add Novatek NT35596 panel driver Jagan Teki
2019-03-31 7:23 ` 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=5ca06105.1c69fb81.8e827.7f26@mx.google.com \
--to=robh@kernel.org \
--cc=airlied@linux.ie \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jagan@amarulasolutions.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michael@amarulasolutions.com \
--cc=ryan@osukl.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).