Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Romain Perier <romain.perier@free-electrons.com>
To: dsaxena@plexity.net, mpm@selenic.com,
	Herbert Xu <herbert@gondor.apana.org.au>
Cc: Gregory Clement <gregory.clement@free-electrons.com>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Romain Perier <romain.perier@free-electrons.com>,
	Nadav Haklai <nadavh@marvell.com>, Omri Itach <omrii@marvell.com>,
	Shadi Ammouri <shadi@marvell.com>,
	Yahuda Yitschak <yehuday@marvell.com>,
	Hanna Hawa <hannah@marvell.com>,
	Neta Zur Hershkovits <neta@marvell.com>,
	Igal Liberman <igall@marvell.com>,
	Marcin Wojtas <mw@semihalf.com>,
	linux-crypto@vger.kernel.org
Subject: [PATCH v2 1/8] dt-bindings: Add vendor prefix for INSIDE Secure
Date: Wed,  7 Sep 2016 17:57:36 +0200	[thread overview]
Message-ID: <20160907155743.6403-2-romain.perier@free-electrons.com> (raw)
In-Reply-To: <20160907155743.6403-1-romain.perier@free-electrons.com>

This commits adds a vendor for the company INSIDE Secure.
See https://www.insidesecure.com, for more details.

Signed-off-by: Romain Perier <romain.perier@free-electrons.com>
---
 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 1992aa9..6a5e872 100644
--- a/Documentation/devicetree/bindings/vendor-prefixes.txt
+++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
@@ -132,6 +132,7 @@ infineon Infineon Technologies
 inforce	Inforce Computing
 ingenic	Ingenic Semiconductor
 innolux	Innolux Corporation
+inside-secure	INSIDE Secure
 intel	Intel Corporation
 intercontrol	Inter Control Group
 invensense	InvenSense Inc.
-- 
2.9.3

  reply	other threads:[~2016-09-07 15:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-07 15:57 [PATCH v2 0/8] Add support for SafeXcel IP-76 to OMAP RNG Romain Perier
2016-09-07 15:57 ` Romain Perier [this message]
2016-09-07 15:57 ` [PATCH v2 2/8] dt-bindings: omap-rng: Document SafeXcel IP-76 device variant Romain Perier
2016-09-07 15:57 ` [PATCH v2 3/8] hwrng: omap - Switch to non-obsolete read API implementation Romain Perier
2016-09-13  9:48   ` Herbert Xu
2016-09-16 10:11     ` Romain Perier
2016-09-07 15:57 ` [PATCH v2 4/8] hwrng: omap - Remove global definition of hwrng Romain Perier
2016-09-07 15:57 ` [PATCH v2 5/8] hwrng: omap - Add support for 128-bit output of data Romain Perier
2016-09-07 15:57 ` [PATCH v2 6/8] hwrng: omap - Don't prefix the probe message with OMAP Romain Perier
2016-09-07 15:57 ` [PATCH v2 7/8] hwrng: omap - Add device variant for SafeXcel IP-76 found in Armada 8K Romain Perier
2016-09-07 15:57 ` [PATCH v2 8/8] arm64: dts: marvell: add TRNG description for Armada 8K CP Romain Perier

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=20160907155743.6403-2-romain.perier@free-electrons.com \
    --to=romain.perier@free-electrons.com \
    --cc=dsaxena@plexity.net \
    --cc=gregory.clement@free-electrons.com \
    --cc=hannah@marvell.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=igall@marvell.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=mw@semihalf.com \
    --cc=nadavh@marvell.com \
    --cc=neta@marvell.com \
    --cc=omrii@marvell.com \
    --cc=shadi@marvell.com \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=yehuday@marvell.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