From: Christopher Nielsen <cnielsen@pobox.com>
To: 9fans@cse.psu.edu
Subject: [9fans] new device
Date: Mon, 22 Jul 2002 12:53:37 -0700 [thread overview]
Message-ID: <20020722195337.GS42736@cassie.foobarbaz.net> (raw)
I started working on a device driver for myrinet night
before last. I have no idea when it will be done, so
please don't ask just yet. I'll keep everyone posted
on the progress.
I need a device character for the driver.
Is it as simple as selecting one not in use and letting
you guys know?
A registry of device characters in use would be useful.
The wiki would be a good place for that. I'll compile
a list from the source and post it to the wiki, if no
one objects too loudly.
--
Christopher Nielsen - Metal-wielding pyro techie
"Those who are willing to trade freedom for security deserve
neither freedom nor security." --Benjamin Franklin
next reply other threads:[~2002-07-22 19:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 19:53 Christopher Nielsen [this message]
2002-07-23 2:11 anothy
2002-07-23 2:29 ` Christopher Nielsen
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=20020722195337.GS42736@cassie.foobarbaz.net \
--to=cnielsen@pobox.com \
--cc=9fans@cse.psu.edu \
/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).