From: "Igor Gueths" <igueths@attbi.com>
To: <speakup@braille.uwo.ca>
Subject: speakup question
Date: Sun, 16 Jun 2002 21:01:57 -0400 [thread overview]
Message-ID: <00c901c2159a$94546160$01273e18@mycomputer> (raw)
Hi all. Does anyone know why Speakup doesn't use the standard conventions when designing kernel modules? In other words, why are the drivers not modularized? Because my plan at least for the dectalk driver was to write the standard module code, and then dump the rest of the driver-specific code into the new re-written version. I am doing this for two reasons. 1. I want to keep the changes as error free as possible. 2. I don't want to have problems after writing new code. And I think most of the driver is fine the way it is. I have other reasons for modularizing the driver, including a project I am currently working on that requires this.
next reply other threads:[~ UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
Igor Gueths [this message]
` John covici
` Igor Gueths
` 'Georgina'
` Igor Gueths
` 'Georgina'
-- strict thread matches above, loose matches on Subject: below --
Speakup question Lui Greco
Michela Botti
` Kirk Reiser
` Jim Wantz
` Kirk Reiser
` Dave Hunt <Dave Hunt
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='00c901c2159a$94546160$01273e18@mycomputer' \
--to=igueths@attbi.com \
--cc=speakup@braille.uwo.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).