From: David Hinds <dhinds@lahmed.stanford.edu>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: Tobias Ringstrom <tori@tellus.mine.nu>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Why not PCMCIA built-in and yenta/i82365 as modules
Date: Tue, 21 Nov 2000 17:28:17 -0800 [thread overview]
Message-ID: <20001121172817.A18265@lahmed.stanford.edu> (raw)
In-Reply-To: <20001121160443.B18150@lahmed.stanford.edu> <200011220110.eAM1Ach414423@saturn.cs.uml.edu>
In-Reply-To: <200011220110.eAM1Ach414423@saturn.cs.uml.edu>; from acahalan@cs.uml.edu on Tue, Nov 21, 2000 at 08:10:38PM -0500
On Tue, Nov 21, 2000 at 08:10:38PM -0500, Albert D. Cahalan wrote:
>
> 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.
Since the core PCMCIA code and the socket driver are equally essential
to do anything useful with PCMCIA, the only reasonable argument I
could see for it would be if you are using one kernel on several
systems, all of which use PCMCIA, but which need different socket
drivers. So you would save... oh... perhaps 2K by having the PCMCIA
shared code in the kernel.
In any case, I don't think it would require much more than modifying
the Config.in for the PCMCIA drivers to support this. My own paranoia
would be that you would be adding a bunch of rarely used permutations
of config options, that would rarely be tested.
-- Dave
-
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:59 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
2000-11-22 1:28 ` David Hinds [this message]
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=20001121172817.A18265@lahmed.stanford.edu \
--to=dhinds@lahmed.stanford.edu \
--cc=acahalan@cs.uml.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®