From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: tegra: add fuses as device randomness
Date: Sun, 15 Sep 2013 12:54:22 +0200 [thread overview]
Message-ID: <CACRpkdZubWnsU2EAMrXxSRNpY7sH1rxkSixSuz_iSD5AfATTBw@mail.gmail.com> (raw)
In-Reply-To: <1379096828-27644-1-git-send-email-swarren@wwwdotorg.org>
On Fri, Sep 13, 2013 at 8:27 PM, Stephen Warren <swarren@wwwdotorg.org> wrote:
> From: Stephen Warren <swarren@nvidia.com>
>
> Various fuses on Tegra include information that's unique to an individual
> chip, or a subset of chips. Call add_device_randomness() with this data
> to perturb the initial state of the random pool.
>
> Suggested-by: Linus Walleij <linus.walleij@linaro.org>
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
Nice! Acked-by FWIW.
Yours,
Linus Walleij
next prev parent reply other threads:[~2013-09-15 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 18:27 [PATCH] ARM: tegra: add fuses as device randomness Stephen Warren
2013-09-15 10:54 ` Linus Walleij [this message]
2013-09-17 20:05 ` Stephen Warren
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=CACRpkdZubWnsU2EAMrXxSRNpY7sH1rxkSixSuz_iSD5AfATTBw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).