From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/2] devicetree: Add vendor prefix for Rikomagic
Date: Fri, 14 Oct 2016 20:21:46 +0200 [thread overview]
Message-ID: <7746988.aAT8rmUZDV@phil> (raw)
In-Reply-To: <d51c7719a314f723a0a69b932997502a2fe0e3ee.1475957884.git.paweljarosz3691@gmail.com>
Am Samstag, 8. Oktober 2016, 22:22:05 CEST schrieb Pawe? Jarosz:
> Add Rikomagic to vendor-prefixes.txt
>
> Signed-off-by: Pawe? Jarosz <paweljarosz3691@gmail.com>
> ---
>
> Changes in v2:
> - none
>
> Changes in v3:
> - none
>
> 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
> 69caf14..3edfa08 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.txt
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
> @@ -224,6 +224,7 @@ realtek Realtek Semiconductor Corp.
> renesas Renesas Electronics Corporation
> richtek Richtek Technology Corporation
> ricoh Ricoh Co. Ltd.
> +rikomagic Rikomagic
^ Rikomagic Tech Corp. Ltd
(according to http://www.rikomagic.com/en/index.html)
But I can change that myself. I'll just need to wait a bit more if Rob or Mark
want to Ack this vendor-prefix addition.
Heiko
next prev parent reply other threads:[~2016-10-14 18:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-08 20:21 [PATCH v3 0/2] Add MK808 RK3066 device Paweł Jarosz
2016-10-08 20:22 ` [PATCH v3 1/2] devicetree: Add vendor prefix for Rikomagic Paweł Jarosz
2016-10-14 18:21 ` Heiko Stuebner [this message]
2016-10-14 18:55 ` Paweł Jarosz
2016-10-14 21:10 ` Rob Herring
2016-10-08 20:22 ` [PATCH v3 2/2] ARM: dts: rockchip: Add rk3066 MK808 board Paweł Jarosz
2016-10-09 13:38 ` Shawn Lin
2016-10-21 16:18 ` [PATCH v3 0/2] Add MK808 RK3066 device Heiko Stuebner
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=7746988.aAT8rmUZDV@phil \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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