LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: 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, herbert@gondor.apana.org.au,
	linux-crypto@vger.kernel.org, mpm@selenic.com,
	Mark Rutland <mark.rutland@arm.com>, Ray Jui <rjui@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	"moderated list:BROADCOM IPROC ARM ARCHITECTURE" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] dt-bindings: rng: Document BCM7211 RNG compatible string
Date: Thu, 13 Jun 2019 14:16:30 -0600	[thread overview]
Message-ID: <20190613201630.GA29776@bogus> (raw)
In-Reply-To: <ce516362-658f-cde3-9be8-0e092f554782@gmail.com>

On Fri, Jun 07, 2019 at 11:57:49AM -0700, Florian Fainelli wrote:
> On 5/10/19 10:31 AM, Florian Fainelli wrote:
> > BCM7211 features a RNG200 block, document its compatible string.
> > 
> > Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> 
> Rob, does this look okay to you?

Yes, sorry, a bit behind on reviews.

  reply	other threads:[~2019-06-13 20:16 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 [this message]
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
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=20190613201630.GA29776@bogus \
    --to=robh@kernel.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mpm@selenic.com \
    --cc=rjui@broadcom.com \
    --cc=sbranden@broadcom.com \
    --cc=stefan.wahren@i2se.com \
    --cc=wahrenst@gmx.net \
    --subject='Re: [PATCH 1/2] dt-bindings: rng: Document BCM7211 RNG compatible string' \
    /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

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).