From: Florian Fainelli <f.fainelli@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com, stefan.wahren@i2se.com,
wahrenst@gmx.net, linux-crypto@vger.kernel.org, mpm@selenic.com
Subject: Re: [PATCH 0/2] hwrng: Support for 7211 in iproc-rng200
Date: Mon, 17 Jun 2019 14:40:41 -0700 [thread overview]
Message-ID: <09c3e286-320c-3681-7fd6-efa34d53b4aa@gmail.com> (raw)
In-Reply-To: <20190523053736.5jjevtz62lgddxtq@gondor.apana.org.au>
On 5/22/19 10:37 PM, Herbert Xu wrote:
> On Mon, May 20, 2019 at 03:49:12PM -0700, Florian Fainelli wrote:
>> On 5/10/19 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.
>>
>> Herbert, can you apply those patches?
>
> Hi Florian:
>
> Patch 1/2 is missing an ack from Rob.
Rob acked it now, can you take those couple of patches? Thanks!
--
Florian
next prev parent reply other threads:[~2019-06-17 21:40 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 ` [PATCH 0/2] hwrng: Support for 7211 in iproc-rng200 Ray Jui
2019-05-20 22:49 ` Florian Fainelli
2019-05-23 5:37 ` Herbert Xu
2019-06-17 21:40 ` Florian Fainelli [this message]
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=09c3e286-320c-3681-7fd6-efa34d53b4aa@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.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;
as well as URLs for NNTP newsgroup(s).