From: Tommy Reynolds <reynolds@redhat.com>
To: "Joe deBlaquiere" <jadb@redhat.com>
Cc: Jack.Bloch@icn.siemens.com, linux-kernel@vger.kernel.org
Subject: Re: Device driver question
Date: Wed, 15 May 2002 10:16:33 -0500 [thread overview]
Message-ID: <20020515101633.24348d0e.reynolds@redhat.com> (raw)
In-Reply-To: <1021474990.1450.56.camel@uberdog>
[-- Attachment #1: Type: text/plain, Size: 271 bytes --]
Uttered "Joe deBlaquiere" <jadb@redhat.com>, spoke thus:
> How about just write a driver that responds to the interrupt, and write
> a program that does a blocking read from the driver.
Then there's the
printk( KERN_EMERG "Hey, Y'all, let's reboot!\n" );
solution.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2002-05-15 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 13:17 Device driver question Bloch, Jack
2002-05-15 13:36 ` Tommy Reynolds
2002-05-15 15:03 ` Joe deBlaquiere
2002-05-15 15:13 ` Tommy Reynolds
2002-05-15 15:16 ` Tommy Reynolds [this message]
2002-05-16 0:18 ` jw schultz
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=20020515101633.24348d0e.reynolds@redhat.com \
--to=reynolds@redhat.com \
--cc=Jack.Bloch@icn.siemens.com \
--cc=jadb@redhat.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;
as well as URLs for NNTP newsgroup(s).