From: Ray Jui <ray.jui@broadcom.com>
To: Florian Fainelli <f.fainelli@gmail.com>, linux-kernel@vger.kernel.org
Cc: bcm-kernel-feedback-list@broadcom.com, stefan.wahren@i2se.com,
wahrenst@gmx.net, herbert@gondor.apana.org.au,
linux-crypto@vger.kernel.org, mpm@selenic.com
Subject: Re: [PATCH 0/2] hwrng: Support for 7211 in iproc-rng200
Date: Fri, 10 May 2019 14:07:12 -0700 [thread overview]
Message-ID: <b1eb11c0-3aa9-52c1-da4c-e685e4bef48e@broadcom.com> (raw)
In-Reply-To: <20190510173112.2196-1-f.fainelli@gmail.com>
Hi Florian,
On 5/10/2019 10:31 AM, Florian Fainelli wrote:
> Hi Herbert,
>
> This patch series adds support for BCM7211 to the iproc-rng200 driver,
> nothing special besides matching the compatibile string and updating the
> binding document.
>
> Florian Fainelli (2):
> dt-bindings: rng: Document BCM7211 RNG compatible string
> hwrng: iproc-rng200: Add support for 7211
>
> Documentation/devicetree/bindings/rng/brcm,iproc-rng200.txt | 1 +
> drivers/char/hw_random/iproc-rng200.c | 1 +
> 2 files changed, 2 insertions(+)
>
Patch series looks good to me. Thanks!
Ray
next prev parent reply other threads:[~2019-05-10 21:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 17:31 [PATCH 0/2] hwrng: Support for 7211 in iproc-rng200 Florian Fainelli
2019-05-10 17:31 ` [PATCH 1/2] dt-bindings: rng: Document BCM7211 RNG compatible string Florian Fainelli
2019-06-07 18:57 ` Florian Fainelli
2019-06-13 20:16 ` Rob Herring
2019-06-13 20:16 ` Rob Herring
2019-05-10 17:31 ` [PATCH 2/2] hwrng: iproc-rng200: Add support for 7211 Florian Fainelli
2019-05-10 21:07 ` Ray Jui [this message]
2019-05-20 22:49 ` [PATCH 0/2] hwrng: Support for 7211 in iproc-rng200 Florian Fainelli
2019-05-23 5:37 ` Herbert Xu
2019-06-17 21:40 ` Florian Fainelli
2019-06-20 8:05 ` Herbert Xu
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=b1eb11c0-3aa9-52c1-da4c-e685e4bef48e@broadcom.com \
--to=ray.jui@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=stefan.wahren@i2se.com \
--cc=wahrenst@gmx.net \
/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