From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Andrzej Krzysztofowicz <ankry@green.mif.pg.gda.pl>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
andrewm@uow.edu.au, p_gortmaker@yahoo.com,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net #3
Date: Wed, 30 May 2001 06:39:52 -0400 [thread overview]
Message-ID: <3B14CDF8.492356F5@mandrakesoft.com> (raw)
In-Reply-To: <200105300041.CAA04507@green.mif.pg.gda.pl> <29071.991213917@redhat.com>
David Woodhouse wrote:
>
> ankry@green.mif.pg.gda.pl said:
> > -#ifdef CONFIG_ISAPNP
> > +#if defined(CONFIG_ISAPNP) || (defined(CONFIG_ISAPNP_MODULE) && defined(MODULE))
>
> The result here would be a 3c509 module which differs depending on whether
> the ISAPNP module happened to be compiled at the same time or not.
In and of itself, that is an acceptable result. We simply cannot take
into kernel configuration variations between two kernel builds. If you
build your isapnp module with one configuration, and your 3c509 module
with another config, consider yourself lucky that it works at all.
> The ISAPNP-specific parts of the code aren't large. Please consider
> including them unconditionally instead.
I probably agree with you and Paul, but I'll have to give it a bit more
thought. Past a certain point, bus support needs to be in its own
driver, similar to drivers/sound/{sb_card,sb_common}.c. But in this
particular case, that would be overkill.
--
Jeff Garzik | Disbelief, that's why you fail.
Building 1024 |
MandrakeSoft |
next prev parent reply other threads:[~2001-05-30 10:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-30 0:41 [PATCH] net #3 Andrzej Krzysztofowicz
2001-05-30 5:49 ` Paul Gortmaker
2001-05-30 10:53 ` Andrzej Krzysztofowicz
2001-05-30 12:03 ` Keith Owens
2001-05-30 9:11 ` David Woodhouse
2001-05-30 10:11 ` Andrzej Krzysztofowicz
2001-05-30 10:39 ` Jeff Garzik [this message]
2001-05-30 11:02 ` Andrzej Krzysztofowicz
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=3B14CDF8.492356F5@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrewm@uow.edu.au \
--cc=ankry@green.mif.pg.gda.pl \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p_gortmaker@yahoo.com \
/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