From: Rob Herring <robh@kernel.org>
To: Olivier Sobrie <olivier.sobrie@silexinsight.com>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
sebastien.rabou@silexinsight.com,
Herbert Xu <herbert@gondor.apana.org.au>,
devicetree@vger.kernel.org, Waleed Ziad <waleed94ziad@gmail.com>,
Rob Herring <robh+dt@kernel.org>, Matt Mackall <mpm@selenic.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 2/3] dt-bindings: rng: document Silex Insight BA431 hwrng
Date: Fri, 29 May 2020 11:13:34 -0600 [thread overview]
Message-ID: <20200529171334.GA2588610@bogus> (raw)
In-Reply-To: <20200525195606.2941649-3-olivier.sobrie@silexinsight.com>
On Mon, 25 May 2020 21:56:05 +0200, Olivier Sobrie wrote:
> This patch documents the device tree bindings of the BA431 hardware
> random number generator.
>
> This IP is for instance present in the Viper OEM boards sold by Silex
> Insight.
>
> Signed-off-by: Olivier Sobrie <olivier.sobrie@silexinsight.com>
> ---
> .../bindings/rng/silex-insight,ba431-rng.yaml | 36 +++++++++++++++++++
> 1 file changed, 36 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/rng/silex-insight,ba431-rng.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-05-29 17:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 19:56 [PATCH 0/3] hwrng: add support for Silex Insight BA431 Olivier Sobrie
2020-05-25 19:56 ` [PATCH 1/3] dt-bindings: vendor-prefixes: Add Silex Insight vendor prefix Olivier Sobrie
2020-05-29 17:12 ` Rob Herring
2020-05-25 19:56 ` [PATCH 2/3] dt-bindings: rng: document Silex Insight BA431 hwrng Olivier Sobrie
2020-05-29 17:13 ` Rob Herring [this message]
2020-05-25 19:56 ` [PATCH 3/3] hwrng: ba431-rng: add support for " Olivier Sobrie
2020-05-25 20:28 ` Arnd Bergmann
2020-05-26 5:16 ` Olivier Sobrie
2020-05-29 17:12 ` Rob Herring
2020-05-29 20:33 ` Olivier Sobrie
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=20200529171334.GA2588610@bogus \
--to=robh@kernel.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=olivier.sobrie@silexinsight.com \
--cc=robh+dt@kernel.org \
--cc=sebastien.rabou@silexinsight.com \
--cc=waleed94ziad@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.