From: CaT <cat@zip.com.au>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Roman Zippel <zippel@linux-m68k.org>,
hch@lst.de, Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.65
Date: Wed, 19 Mar 2003 02:33:03 +1100 [thread overview]
Message-ID: <20030318153303.GI504@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0303180714140.11305-100000@home.transmeta.com>
On Tue, Mar 18, 2003 at 07:16:06AM -0800, Linus Torvalds wrote:
> On Tue, 18 Mar 2003, CaT wrote:
> > Ahhh. So if I want module support but not use it as a module then I'm
> > SOL?
>
> Well, does it _work_ as a built-in? If it does, just send me a patch for
> the Kconfig file.
Well, I would if I could. I don't actually have the card, I was just
going to compile it in incase I had to use one one day. Saves time not
having to recompile the kernel and I don't wanna waste disk space on
modules (and having to clean them up from old kernel versions etc). My
laptop HD space is precious. :)
> A lot of the PCMCIA stuff (16-bit) historically _only_ works as modules,
> because the old PCMCIA code depended on module unload to do a lot of the
> cleanups that the regular internal eject handling didn't do. But if that
> driver works for you built-in, then the Kconfig file itself is simply just
> wrong.
It might be an idea to modify the help and maybe the error message right
now as at the moment the help indicates that it can be compiled in
without stating any conditions for it, and the error message talks about
some other mysterious component that this one depends on that was selected
as a module and so this one will be, which would send the user off on a
goose chace (like it did me for a wee bit :). Is there a way to
customize that? If so I could make up a patch that clarifies things
more.
--
"Other countries of course, bear the same risk. But there's no doubt his
hatred is mainly directed at us. After all this is the guy who tried to
kill my dad."
- George W. Bush Jr, 'President' of Regime of the United States
September 26, 2002 (from a political fundraiser in Houston, Texas)
next prev parent reply other threads:[~2003-03-18 15:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 22:31 Linux 2.5.65 Linus Torvalds
2003-03-18 0:53 ` John Cherry
2003-03-18 5:22 ` CaT
2003-03-18 8:15 ` Christoph Hellwig
2003-03-18 9:12 ` CaT
2003-03-18 10:08 ` Roman Zippel
2003-03-18 10:35 ` CaT
2003-03-18 10:43 ` Roman Zippel
2003-03-18 10:48 ` John Bradford
2003-03-18 15:16 ` Linus Torvalds
2003-03-18 15:33 ` CaT [this message]
2003-03-18 12:45 ` Remaining occurances of DEVFS_FL_AUTO_DEVNUM in 2.5.65 Adrian Bunk
2003-03-18 15:40 ` Christoph Hellwig
2003-03-18 16:04 ` Christoph Hellwig
2003-03-18 16:24 ` top Stack (l)users for 2.5.65 Jörn Engel
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=20030318153303.GI504@zip.com.au \
--to=cat@zip.com.au \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=zippel@linux-m68k.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