From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Stephan Müller" <smueller@chronox.de>
Cc: Kukjin Kim <kgene@kernel.org>,
Javier Martinez Canillas <javier@osg.samsung.com>,
Matt Mackall <mpm@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-crypto@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>
Subject: Re: [PATCH 1/3] crypto: hw_random - Add new Exynos RNG driver
Date: Fri, 24 Mar 2017 17:58:18 +0300 [thread overview]
Message-ID: <20170324145818.3muyy4cq3gms5len@kozik-lap> (raw)
In-Reply-To: <2090327.CHzkLTTdtg@positron.chronox.de>
On Fri, Mar 24, 2017 at 03:55:22PM +0100, Stephan Müller wrote:
> Am Freitag, 24. März 2017, 15:51:56 CET schrieb Krzysztof Kozlowski:
>
> Hi Krzysztof,
> >
> > I'll use the generated random numbers.
>
> If you do that, may I propse that you update this seed field periodically?
> E.g. with every (or every other) user request for random data, you may update
> that field with new data.
Sounds reasonable. Thanks for feedback, it is much appreciated.
Best regards,
Krzysztof
next prev parent reply other threads:[~2017-03-24 14:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 14:24 [PATCH 0/3] crypto: hw_random - Add new Exynos RNG driver Krzysztof Kozlowski
2017-03-24 14:24 ` [PATCH 1/3] " Krzysztof Kozlowski
2017-03-24 14:37 ` Stephan Müller
2017-03-24 14:43 ` Krzysztof Kozlowski
2017-03-24 14:46 ` Stephan Müller
2017-03-24 14:51 ` Krzysztof Kozlowski
2017-03-24 14:55 ` Stephan Müller
2017-03-24 14:58 ` Krzysztof Kozlowski [this message]
2017-03-24 15:26 ` Bartlomiej Zolnierkiewicz
2017-03-24 15:46 ` Krzysztof Kozlowski
2017-03-24 16:11 ` Bartlomiej Zolnierkiewicz
2017-03-24 16:19 ` Krzysztof Kozlowski
2017-03-24 16:45 ` Bartlomiej Zolnierkiewicz
2017-03-24 17:01 ` Krzysztof Kozlowski
2017-03-24 14:24 ` [PATCH 2/3] ARM: exynos_defconfig: Enable Exynos RNG and user-space crypto API Krzysztof Kozlowski
2017-03-24 14:24 ` [PATCH 3/3] ARM: multi_v7_defconfig: " Krzysztof Kozlowski
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=20170324145818.3muyy4cq3gms5len@kozik-lap \
--to=krzk@kernel.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=javier@osg.samsung.com \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=olof@lixom.net \
--cc=smueller@chronox.de \
/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