From: David Gibson <david@gibson.dropbear.id.au>
To: Anton Blanchard <anton@samba.org>
Cc: devicetree@vger.kernel.org, Rob Herring <rob.herring@calxeda.com>,
Paul Mackerras <paulus@samba.org>,
Grant Likely <grant.likely@linaro.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] of: Feed entire flattened device tree into the random pool
Date: Thu, 25 Jul 2013 14:42:34 +1000 [thread overview]
Message-ID: <20130725044234.GI6806@voom.fritz.box> (raw)
In-Reply-To: <20130725143031.16af0a96@kryten>
[-- Attachment #1: Type: text/plain, Size: 662 bytes --]
On Thu, Jul 25, 2013 at 02:30:31PM +1000, Anton Blanchard wrote:
>
> Hi Michael,
>
> > But why not put the initcall in drivers/of/fdt.c, that way it's not
> > early but it's still common ?
>
> Good idea! How does this look? So long as it happens before
> module_init(rand_initialize) we should be good.
This must be some strange new meaning of the word "random" of which I
was not previously aware. But I guess it's marginally better than
nothing.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-07-25 4:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 2:51 [PATCH] powerpc: Feed entire flattened device tree into the random pool Anton Blanchard
2013-07-25 3:17 ` Michael Ellerman
2013-07-25 4:30 ` [PATCH] of: " Anton Blanchard
2013-07-25 4:42 ` David Gibson [this message]
2013-07-28 4:49 ` Grant Likely
2013-07-29 3:11 ` Anton Blanchard
2013-08-29 20:47 ` Grant Likely
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=20130725044234.GI6806@voom.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=anton@samba.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=rob.herring@calxeda.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;
as well as URLs for NNTP newsgroup(s).