From: John Crispin <blogic-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
To: Ralf Baechle <ralf-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org>
Cc: linux-mips-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: [PATCH V2 1/6] DT: add vendor prefixes for Ralink
Date: Tue, 16 Apr 2013 11:12:37 +0200 [thread overview]
Message-ID: <1366103562-21463-1-git-send-email-blogic@openwrt.org> (raw)
Signed-off-by: John Crispin <blogic-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
---
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 19e1ef7..6527412 100644
--- a/Documentation/devicetree/bindings/vendor-prefixes.txt
+++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
@@ -41,6 +41,7 @@ onnn ON Semiconductor Corp.
picochip Picochip Ltd
powervr PowerVR (deprecated, use img)
qcom Qualcomm, Inc.
+ralink Mediatek/Ralink Technology Corp.
ramtron Ramtron International
realtek Realtek Semiconductor Corp.
renesas Renesas Electronics Corporation
--
1.7.10.4
next reply other threads:[~2013-04-16 9:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 9:12 John Crispin [this message]
2013-04-16 9:12 ` [PATCH V2 3/6] DT: MIPS: ralink: clean up RT3050 dtsi and dts file John Crispin
2013-04-16 9:12 ` [PATCH V2 4/6] DT: MIPS: ralink: add RT2880 dts files John Crispin
[not found] ` <1366103562-21463-1-git-send-email-blogic-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
2013-04-16 9:12 ` [PATCH V2 2/6] DT: add documentation for the Ralink MIPS SoCs John Crispin
2013-04-16 9:12 ` [PATCH V2 5/6] DT: MIPS: ralink: add RT3883 dts files John Crispin
2013-04-16 13:00 ` Sergei Shtylyov
2013-04-16 9:12 ` [PATCH V2 6/6] DT: MIPS: ralink: add MT7620A " John Crispin
2013-04-16 12:59 ` Sergei Shtylyov
2013-04-18 12:50 ` [PATCH V2 1/6] DT: add vendor prefixes for Ralink Grant Likely
2013-04-18 12:46 ` John Crispin
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=1366103562-21463-1-git-send-email-blogic@openwrt.org \
--to=blogic-p3rkhjxn3npafugrpc6u6w@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linux-mips-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org \
--cc=ralf-6z/3iImG2C8G8FEW9MqTrA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).