public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@suse.de>
To: Manon Goo <manon@manon.de>
Cc: "White, Charles" <Charles.White@COMPAQ.com>,
	Arrays <Arrays@COMPAQ.com>,
	linux-kernel@vger.kernel.org,
	"Markus Schröder" <schroeder.markus@allianz.de>
Subject: Re: Hooks for random device entropy generation missing in cpqarray.c
Date: Wed, 20 Mar 2002 17:16:55 +0100	[thread overview]
Message-ID: <20020320171655.F5094@suse.de> (raw)
In-Reply-To: <A2C35BB97A9A384CA2816D24522A53BB01E88B79@cceexc18.americas.cpqc <5013428.1016644014@eva.dhcp.gimlab.org>

On Wed, Mar 20, 2002 at 05:06:54PM +0100, Manon Goo wrote:
 > I have a quick and drity patch for 1 contorlller:
 > ...
 >
 > --On Mittwoch, 20. März 2002 8:25 Uhr -0600 "White, Charles" 
 > <Charles.White@COMPAQ.com> wrote:
 > 
 > >Yes.. I was reported that it some how got dropped from our 2.4 version of
 > >the driver..  DON'T add add_interrupt_randomness, just add "|
 > >SA_SAMPLE_RANDOM" to the call to request_irq.
 > How would I do this for the cpqarray ?

 Exactly like Charles explained how to. See also...
 http://www.codemonkey.org.uk/patches/merged/2.5.4/dj2/random-cpqirq.diff
 if it still isnt' clear.
-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

       reply	other threads:[~2002-03-20 16:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <A2C35BB97A9A384CA2816D24522A53BB01E88B79@cceexc18.americas.cpqc <5013428.1016644014@eva.dhcp.gimlab.org>
2002-03-20 16:16 ` Dave Jones [this message]
2002-03-20 16:29   ` Hooks for random device entropy generation missing in cpqarray.c Manon Goo
2002-03-20 21:07 Stephen Cameron
2002-03-20 21:24 ` Manon Goo
  -- strict thread matches above, loose matches on Subject: below --
2002-03-20 14:25 White, Charles
2002-03-20 16:06 ` Manon Goo
2002-03-20 13:33 Manon Goo
2002-03-20 14:38 ` Zwane Mwaikambo
2002-03-20 15:39   ` Alan Cox
2002-03-20 15:39   ` Manon Goo
2002-03-20 15:42     ` Zwane Mwaikambo

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=20020320171655.F5094@suse.de \
    --to=davej@suse.de \
    --cc=Arrays@COMPAQ.com \
    --cc=Charles.White@COMPAQ.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manon@manon.de \
    --cc=schroeder.markus@allianz.de \
    /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