From: Chris Peterson <cpeterso@cpeterso.com>
To: Matt Mackall <mpm@selenic.com>
Cc: Robin Getz <rgetz@blackfin.uclinux.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: IRQF_SAMPLE_RANDOM question...
Date: Thu, 9 Apr 2009 18:29:10 -0700 [thread overview]
Message-ID: <a24804730904091829k167668f1y6e546693b2f8e5da@mail.gmail.com> (raw)
In-Reply-To: <1239296459.31467.142.camel@calx>
> Hmm, this is a purely internal interface. Not sure if we need to bother
> with scheduling it. My plan was to simply get the new code in and sweep
> the kernel.
Matt, sounds like you're volunteering? :)
>From my understanding, the roadmap looks something like:
1. Add checkpatch warning about IRQF_SAMPLE_RANDOM
2. Add any new add_*_randomness() functions (e.g. RTC and main clocks?
Serial or USB interrupts?)
3. Remove IRQF_SAMPLE_RANDOM macro (and checkpatch warning)
4. Add "pragmatic entropy accounting model"?
chris
next prev parent reply other threads:[~2009-04-10 1:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 18:30 IRQF_SAMPLE_RANDOM question Robin Getz
2009-04-06 18:40 ` Jeff Garzik
2009-04-06 18:44 ` Stephen Hemminger
2009-04-06 18:49 ` Jeff Garzik
2009-04-07 8:27 ` Jeremy Fitzhardinge
2009-04-06 19:22 ` Robin Getz
2009-04-06 19:00 ` Alan Cox
2009-04-06 19:01 ` Matt Mackall
2009-04-06 22:09 ` Sven-Haegar Koch
2009-04-06 23:35 ` Jeff Garzik
2009-04-07 21:58 ` Robin Getz
2009-04-07 22:25 ` Jeff Garzik
2009-04-07 0:16 ` Matt Mackall
2009-04-07 0:30 ` Jeff Garzik
2009-04-07 11:16 ` Robin Getz
2009-04-07 14:57 ` Matt Mackall
2009-04-07 21:39 ` Chris Peterson
2009-04-07 22:30 ` Robin Getz
2009-04-08 21:53 ` Gilles Espinasse
2009-04-08 23:16 ` Chris Friesen
2009-04-09 4:24 ` Robin Getz
2009-04-07 21:44 ` Robin Getz
2009-04-08 19:51 ` Matt Mackall
2009-04-09 13:54 ` Robin Getz
2009-04-09 17:00 ` Matt Mackall
2009-04-10 0:41 ` Robin Getz
2009-04-10 1:29 ` Chris Peterson [this message]
2009-04-10 2:27 ` Matt Mackall
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=a24804730904091829k167668f1y6e546693b2f8e5da@mail.gmail.com \
--to=cpeterso@cpeterso.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=netdev@vger.kernel.org \
--cc=rgetz@blackfin.uclinux.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).