From: Sascha Hauer <s.hauer@pengutronix.de>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v8 0/7] upstream hwrng framework
Date: Fri, 24 Mar 2017 07:13:43 +0100 [thread overview]
Message-ID: <20170324061343.yabwryik7umt5ud5@pengutronix.de> (raw)
In-Reply-To: <20170322091439.18187-1-o.rempel@pengutronix.de>
On Wed, Mar 22, 2017 at 10:14:32AM +0100, Oleksij Rempel wrote:
> changes v1:
> - initial version
>
> changes v2:
> - drop Freescale RNGC for now. It need more testing
> - add caamrng port
> - fix hwrng_init()
> - fix hwrng_get_first check in get_random_bytes
>
> changes v3:
> - check if hwrng_get_data returns error
> - provide /dev/randomdd random device
>
> changes v4:
> - provide get_crypto_bytes() interface.
> - add CONFIG_ALLOW_PRNG_FALLBACK
> - make cmd_password use get_crypto_bytes
> - add cmd_seed
>
> changes v5:
> - make cmd_seed fail if no VALUE is set
>
> changes v6:
> - reword second patch and remove useless if (bytes > lenght) check.
>
> changes v7:
> - use numbered names: /dev/hwrngN
> - allow to use aliases for device name.
>
> changes v8:
> - remove comment about nonexisting priv variable
> - make hwrng_get_first() static inline with return error if CONFIG_HWRNG
> is disabled.
>
> Oleksij Rempel (6):
> lib: random: add get_crypto_bytes interface and use HWRNG if posssible
> caamrng: port to hwrng framework
> fs: add prng device
> crypto: caam - fix RNG buffer cache alignment
> common: password: make use of get_crypto_bytes
> add seed command
>
> Steffen Trumtrar (1):
> drivers: add simple hw_random implementation
Applied, thanks
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2017-03-24 6:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 9:14 Oleksij Rempel
2017-03-22 9:14 ` [PATCH v8 1/7] drivers: add simple hw_random implementation Oleksij Rempel
2017-03-22 9:14 ` [PATCH v8 2/7] lib: random: add get_crypto_bytes interface and use HWRNG if posssible Oleksij Rempel
2017-03-22 9:14 ` [PATCH v8 3/7] caamrng: port to hwrng framework Oleksij Rempel
2017-03-22 9:14 ` [PATCH v8 4/7] fs: add prng device Oleksij Rempel
2017-03-22 9:14 ` [PATCH v8 5/7] crypto: caam - fix RNG buffer cache alignment Oleksij Rempel
2017-03-22 9:14 ` [PATCH v8 6/7] common: password: make use of get_crypto_bytes Oleksij Rempel
2017-03-22 9:14 ` [PATCH v8 7/7] add seed command Oleksij Rempel
2017-03-24 6:13 ` Sascha Hauer [this message]
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=20170324061343.yabwryik7umt5ud5@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=o.rempel@pengutronix.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