From: Rob Herring <robh@kernel.org>
To: sean.wang@mediatek.com
Cc: herbert@gondor.apana.org.au, mpm@selenic.com,
mark.rutland@arm.com, clabbe.montjoie@gmail.com,
prasannatsmkumar@gmail.com, romain.perier@free-electrons.com,
shannon.nelson@oracle.com, weiyongjun1@huawei.com,
devicetree@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, keyhaede@gmail.com
Subject: Re: [PATCH 1/2] dt-bindings: hwrng: Add Mediatek hardware random generator bindings
Date: Wed, 19 Apr 2017 16:23:25 -0500 [thread overview]
Message-ID: <20170419212325.y3t2vohmsuhet2xu@rob-hp-laptop> (raw)
In-Reply-To: <1492067108-14748-2-git-send-email-sean.wang@mediatek.com>
On Thu, Apr 13, 2017 at 03:05:07PM +0800, sean.wang@mediatek.com wrote:
> From: Sean Wang <sean.wang@mediatek.com>
>
> Document the devicetree bindings for Mediatek random number
> generator which could be found on MT7623 SoC or other similar
> Mediatek SoCs.
>
> Signed-off-by: Sean Wang <sean.wang@mediatek.com>
> ---
> Documentation/devicetree/bindings/rng/mtk-rng.txt | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/rng/mtk-rng.txt
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2017-04-19 21:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 7:05 [PATCH 0/2] hwrng: mtk: add support for hardware random generator on MT7623 SoC sean.wang
2017-04-13 7:05 ` [PATCH 1/2] dt-bindings: hwrng: Add Mediatek hardware random generator bindings sean.wang
2017-04-19 21:23 ` Rob Herring [this message]
2017-04-13 7:05 ` [PATCH 2/2] hwrng: mtk: Add driver for hardware random generator on MT7623 SoC sean.wang
2017-04-13 8:39 ` PrasannaKumar Muralidharan
2017-04-14 3:58 ` Sean Wang
2017-04-14 4:57 ` PrasannaKumar Muralidharan
2017-04-13 11:06 ` Corentin Labbe
2017-04-14 3:38 ` Sean Wang
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=20170419212325.y3t2vohmsuhet2xu@rob-hp-laptop \
--to=robh@kernel.org \
--cc=clabbe.montjoie@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=keyhaede@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mpm@selenic.com \
--cc=prasannatsmkumar@gmail.com \
--cc=romain.perier@free-electrons.com \
--cc=sean.wang@mediatek.com \
--cc=shannon.nelson@oracle.com \
--cc=weiyongjun1@huawei.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;
as well as URLs for NNTP newsgroup(s).