From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: thierry.reding@gmail.com, robh+dt@kernel.org
Cc: pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Boris BREZILLON <boris.brezillon@free-electrons.com>
Subject: Re: [PATCH] devicetree: Add vendor prefix for Foxlink Group
Date: Wed, 29 Apr 2015 17:16:45 +0200 [thread overview]
Message-ID: <5540F5DD.5010101@atmel.com> (raw)
In-Reply-To: <1427213575-27340-1-git-send-email-nicolas.ferre@atmel.com>
Le 24/03/2015 17:12, Nicolas Ferre a écrit :
> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> ---
> Thierry,
>
> Boris added the support for a Foxlink panel in this commit: 102932b0e474
> (drm/panel: add support for Foxlink FL500WVR00-A0T panel). Here is the vendor
> prefix.
Ping?
>
> Bye,
>
> Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt b/Documentation/devicetree/bindings/vendor-prefixes.txt
> index 1b0f5b797cd5..e9fca088ba1a 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.txt
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
> @@ -73,6 +73,7 @@ everspin Everspin Technologies, Inc.
> excito Excito
> fcs Fairchild Semiconductor
> firefly Firefly
> +foxlink Foxlink Group
> fsl Freescale Semiconductor
> GEFanuc GE Fanuc Intelligent Platforms Embedded Systems, Inc.
> gef GE Fanuc Intelligent Platforms Embedded Systems, Inc.
>
--
Nicolas Ferre
next prev parent reply other threads:[~2015-04-29 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 16:12 [PATCH] devicetree: Add vendor prefix for Foxlink Group Nicolas Ferre
2015-04-29 15:16 ` Nicolas Ferre [this message]
2015-04-29 15:31 ` Rob Herring
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=5540F5DD.5010101@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=boris.brezillon@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@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).