From: "Theodore Ts'o" <tytso@mit.edu>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com
Subject: Re: mfd: wm831x: Feed the device UUID into device_add_randomness()
Date: Fri, 6 Jul 2012 17:23:33 -0400 [thread overview]
Message-ID: <20120706212333.GA4877@thunk.org> (raw)
In-Reply-To: <1341519801-5904-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On Thu, Jul 05, 2012 at 08:23:21PM -0000, Mark Brown wrote:
> wm831x devices contain a unique ID value. Feed this into the newly added
> device_add_randomness() to add some per device seed data to the pool.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
>
> add_device_randomness() has only just been added in -next, this will
> need to either wait until after the merge window or be merged along with
> the patch adding it.
Thanks, I've added this to the /dev/random git tree.
- Ted
prev parent reply other threads:[~2012-07-06 21:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 20:23 [PATCH] mfd: wm831x: Feed the device UUID into device_add_randomness() Mark Brown
2012-07-06 21:23 ` Theodore Ts'o [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=20120706212333.GA4877@thunk.org \
--to=tytso@mit.edu \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sameo@linux.intel.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