From: Valentin Longchamp <valentin.longchamp@keymile.com>
To: Scott Wood <scottwood@freescale.com>, linuxppc-dev@lists.ozlabs.org
Cc: devicetree@vger.kernel.org,
Valentin Longchamp <valentin.longchamp@keymile.com>
Subject: [PATCH v4 1/3] devicetree: bindings: add Zarlink to the vendor prefixes
Date: Tue, 22 Apr 2014 11:30:29 +0200 [thread overview]
Message-ID: <1398159031-10110-2-git-send-email-valentin.longchamp@keymile.com> (raw)
In-Reply-To: <1398159031-10110-1-git-send-email-valentin.longchamp@keymile.com>
Even though the company belongs to Microsemi, many chips are still
labeled as Zarlink. Among them is the family of network clock generators,
the zl3034x.
Signed-off-by: Valentin Longchamp <valentin.longchamp@keymile.com>
---
Changes in v4: None
Changes in v3: None
Changes in v2:
- add a patch so that the Zarlink vendor prefix is defined
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 0f01c9b..93cc7dc 100644
--- a/Documentation/devicetree/bindings/vendor-prefixes.txt
+++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
@@ -119,3 +119,4 @@ wlf Wolfson Microelectronics
wm Wondermedia Technologies, Inc.
xes Extreme Engineering Solutions (X-ES)
xlnx Xilinx
+zarlink Zarlink Semiconductor
--
1.8.0.1
next prev parent reply other threads:[~2014-04-22 9:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 9:30 [PATCH v4 0/3] Support of the kmcoge4 board Valentin Longchamp
2014-04-22 9:30 ` Valentin Longchamp [this message]
2014-04-22 9:30 ` [PATCH v4 2/3] devcietree: bindings: add some MFD Keymile FPGAs Valentin Longchamp
2014-04-22 9:30 ` [PATCH v4 3/3] powerpc/mpc85xx: add support for Keymile's kmcoge4 board Valentin Longchamp
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=1398159031-10110-2-git-send-email-valentin.longchamp@keymile.com \
--to=valentin.longchamp@keymile.com \
--cc=devicetree@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.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).