From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: test11-pre6
Date: Fri, 17 Nov 2000 06:57:59 -0500 [thread overview]
Message-ID: <3A151D47.172D67E@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10011161832460.803-100000@penguin.transmeta.com> <20001117203325.A15841@metastasis.f00f.org>
Chris Wedgwood wrote:
> There are 'hotplug' additions -- these now mean the networking code
> won't build without "CONFIG_HOTPLUG=y".
>
> What is the correct fix here; fix the networking code or just take
> this option out and ensure hotplug functionality is no longer
> compile-time dependent (always compiled in) ?
Surround the networking code with CONFIG_HOTPLUG. A patch has already
been posted to lkml.
Jeff
--
Jeff Garzik |
Building 1024 | The chief enemy of creativity is "good" sense
MandrakeSoft | -- Picasso
-
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-17 12:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-17 2:33 test11-pre6 Linus Torvalds
2000-11-17 3:45 ` test11-pre6 Jeff V. Merkey
2000-11-17 7:30 ` test11-pre6 Erik Andersen
2000-11-17 8:30 ` test11-pre6 David Lang
2000-11-17 8:53 ` test11-pre6 Jeff V. Merkey
2000-11-17 16:11 ` test11-pre6 Mike A. Harris
2000-11-17 7:33 ` test11-pre6 Chris Wedgwood
2000-11-17 11:57 ` Jeff Garzik [this message]
2000-11-17 9:06 ` [PATCH-2.4.0-10] vgacon.c jani
2000-11-17 10:37 ` test11-pre6 David Woodhouse
2000-11-17 11:51 ` [patch] hotplug fixes test11-pre6 Tigran Aivazian
-- strict thread matches above, loose matches on Subject: below --
2000-11-17 3:02 test11-pre6 Ying Chen/Almaden/IBM
2000-11-17 3:09 ` test11-pre6 David S. Miller
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=3A151D47.172D67E@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.