From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Ion Badulescu <ionut@moisil.cs.columbia.edu>
Cc: Linux Knernel Mailing List <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@conectiva.com.br>
Subject: Re: Modular versus non-modular ISAPNP
Date: Tue, 13 Mar 2001 05:03:21 -0500 [thread overview]
Message-ID: <3AADF069.7B22EF1F@mandrakesoft.com> (raw)
In-Reply-To: <200103130403.f2D43Kh10666@moisil.dev.hydraweb.com>
Ion Badulescu wrote:
>
> On Mon, 12 Mar 2001 22:02:12 -0500, Jeff Garzik <jgarzik@mandrakesoft.com> wrote:
>
> > It is highly recommended to always compile with CONFIG_ISAPNP=y due to
> > these differences. If you grep around for CONFIG_ISAPNP versus
> > CONFIG_ISAPNP_MODULE, you'll see that many drivers are woefully
> > unprepared for isapnp support compiled as a module.
>
> Another entry for the Kernel Janitor's List, perhaps?
Yep.. grep for CONFIG_ISAPNP, look at the code, and evaluate it to make
sure that isapnp works for that drivers regardless of whether
CONFIG_ISAPNP -or- CONFIG_ISAPNP_MODULE is defined.
Jeff
--
Jeff Garzik | May you have warm words on a cold evening,
Building 1024 | a full mooon on a dark night,
MandrakeSoft | and a smooth road all the way to your door.
prev parent reply other threads:[~2001-03-13 10:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-13 1:18 PATCH - compile fix for 3c509.c in 2.4.3-pre3 Neil Brown
2001-03-13 1:47 ` Jeff Garzik
[not found] ` <15021.36013.606715.731130@notabene.cse.unsw.edu.au>
2001-03-13 3:02 ` Modular versus non-modular ISAPNP (was Re: PATCH - compile fix for 3c509.c in 2.4.3-pre3) Jeff Garzik
2001-03-13 4:03 ` Modular versus non-modular ISAPNP Ion Badulescu
2001-03-13 10:03 ` Jeff Garzik [this message]
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=3AADF069.7B22EF1F@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=acme@conectiva.com.br \
--cc=ionut@moisil.cs.columbia.edu \
--cc=linux-kernel@vger.kernel.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