From: Chris Friesen <cfriesen@nortelnetworks.com>
To: linux-kernel@vger.kernel.org
Subject: why no call to add_interrupt_randomness() on PPC?
Date: Wed, 22 Aug 2001 10:39:44 -0400 [thread overview]
Message-ID: <3B83C430.7E5F59C3@nortelnetworks.com> (raw)
With all the talk about randomness, I went to see where my current system
(2.2.19 on PPC) was getting random numbers from. I was kind of surprised to see
that there is no call to add_interrupt_randomness() in arch/ppc/kernel/irq.c.
Does anyone know why this call is not present in ppc_irq_dispatch_handler()?
Would it be appropriate for me to make a patch for this? Who would be the
appropriate person to send this to?
Thanks,
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next reply other threads:[~2001-08-22 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-22 14:39 Chris Friesen [this message]
[not found] <3B83C430.7E5F59C3@nortelnetworks.com.suse.lists.linux.kernel>
2001-08-22 15:26 ` why no call to add_interrupt_randomness() on PPC? Andi Kleen
2001-08-22 15:37 ` Chris Friesen
2001-08-22 15:47 ` Alex Bligh - linux-kernel
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=3B83C430.7E5F59C3@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.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