From: "Albert D. Cahalan" <acahalan@cs.uml.edu>
To: dhinds@lahmed.stanford.edu (David Hinds)
Cc: tori@tellus.mine.nu (Tobias Ringstrom),
linux-kernel@vger.kernel.org (Kernel Mailing List)
Subject: Re: Why not PCMCIA built-in and yenta/i82365 as modules
Date: Tue, 21 Nov 2000 20:10:38 -0500 (EST) [thread overview]
Message-ID: <200011220110.eAM1Ach414423@saturn.cs.uml.edu> (raw)
In-Reply-To: <20001121160443.B18150@lahmed.stanford.edu> from "David Hinds" at Nov 21, 2000 04:04:44 PM
>> The subject says it all. Is there any particular (technical) reason
>> why I must have both the generic pcmcia code and the controller
>> support built-in, or build all of them as modules?
>
> Is there a technical reason for this? Not that I know of; but then I
> also cannot think of a good reason for wanting, say, the generic code
> built in but the controller support as modules. I do see reasonable
> arguments for all-builtin or all-modules.
Hmmm, I'm not the only one who doesn't like modules depending
on other modules. I suppose this is part paranoia about extra
complexity leading to problems, and part desire to avoid the
module overhead for common code that will most likely get used.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-22 1:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-21 22:34 Tobias Ringstrom
2000-11-22 0:04 ` David Hinds
2000-11-22 1:10 ` Albert D. Cahalan [this message]
2000-11-22 1:28 ` David Hinds
2000-11-22 1:44 ` Horst von Brand
2000-11-22 1:50 ` David Hinds
2000-11-22 10:54 ` Tobias Ringstrom
2000-11-22 10:25 ` Matti Aarnio
2000-11-22 12:29 ` Alan Cox
2000-11-24 17:06 ` Oliver Xymoron
2000-11-22 11:05 ` David Woodhouse
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=200011220110.eAM1Ach414423@saturn.cs.uml.edu \
--to=acahalan@cs.uml.edu \
--cc=dhinds@lahmed.stanford.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=tori@tellus.mine.nu \
/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
all inboxes | Powered by JetHome®