From: Arnd Bergmann <arnd@arndb.de>
To: Michael Buesch <mb@bu3sch.de>
Cc: akpm@osdl.org, Deepak Saxena <dsaxena@plexity.net>,
bcm43xx-dev@lists.berlios.de, linux-kernel@vger.kernel.org,
Sergey Vlasov <vsu@altlinux.ru>
Subject: Re: [patch 0/6] New Generic HW RNG (#2)
Date: Sun, 7 May 2006 20:39:07 +0200 [thread overview]
Message-ID: <200605072039.08702.arnd@arndb.de> (raw)
In-Reply-To: <20060507143806.465264000@pc1>
On Sunday 07 May 2006 16:38, Michael Buesch wrote:
> Second try. Various fixes included. This does even compile (and work) now. :)
>
It would be good to give the patches more descriptive names, currently
they all have the same subject lines, which is not really helpful.
> The userspace RNG daemon can later be updated to select the RNG through
> /sys/class/misc/hw_random/ for convenience. For now it is sufficient to
> use cat and echo -n on the sysfs attributes.
When you're making the behaviour of hw_random configurable, maybe you could
also add an option to automatically use the current hw_random driver to
feed the /dev/random entropy pool on systems where the administrator trusts
its randomness.
Arnd <><
next prev parent reply other threads:[~2006-05-07 18:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-07 14:38 [patch 0/6] New Generic HW RNG (#2) Michael Buesch
2006-05-07 14:38 ` [patch 1/6] " Michael Buesch
2006-05-07 14:38 ` [patch 2/6] " Michael Buesch
2006-05-07 14:38 ` [patch 3/6] " Michael Buesch
2006-05-07 15:22 ` Sergey Vlasov
2006-05-07 15:39 ` Michael Buesch
2006-05-07 16:24 ` Sergey Vlasov
2006-05-07 14:38 ` [patch 4/6] " Michael Buesch
2006-05-07 14:38 ` [patch 5/6] " Michael Buesch
2006-05-07 14:38 ` [patch 6/6] " Michael Buesch
2006-05-07 18:39 ` Arnd Bergmann [this message]
2006-05-07 18:50 ` [patch 0/6] " Michael Buesch
2006-05-07 18:47 ` Arnd Bergmann
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=200605072039.08702.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@osdl.org \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=dsaxena@plexity.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=vsu@altlinux.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.