From: Adrian Bunk <bunk@fs.tum.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-net@vger.kernel.org, linux-kernel@vger.kernel.or
Subject: [2.6 patch] CONFIG_MII requires only CONFIG_NET
Date: Fri, 13 Aug 2004 12:22:02 +0200 [thread overview]
Message-ID: <20040813102202.GT13377@fs.tum.de> (raw)
Hi Jeff,
the patch below still applies against 2.6.8-rc4-mm1.
Could you comment on it and apply it if it's correct?
TIA
Adrian
But trying it out CONFIG_MII=y seems to at least compile with
CONFIG_NET_ETHERNET=n.
@Jeff:
It seems, CONFIG_MII doesn't actually require CONFIG_NET_ETHERNET?
Could you comment on the following patch?
Signed-off-by: Adrian Bunk <bunk@fs.tum.de>
--- linux-2.6.6-rc1-mm1-full/drivers/net/Kconfig.old 2004-04-20 00:48:27.000000000 +0200
+++ linux-2.6.6-rc1-mm1-full/drivers/net/Kconfig 2004-04-20 01:07:51.000000000 +0200
@@ -151,6 +151,15 @@
If you don't have this card, of course say N.
+config MII
+ tristate "Generic Media Independent Interface device support"
+ depends on NET
+ help
+ Most ethernet controllers have MII transceiver either as an external
+ or internal device. It is safe to say Y or M here even if your
+ ethernet card lack MII.
+
+
if NETDEVICES
source "drivers/net/arcnet/Kconfig"
endif
@@ -188,14 +197,6 @@
kernel: saying N will just cause the configurator to skip all
the questions about Ethernet network cards. If unsure, say N.
-config MII
- tristate "Generic Media Independent Interface device support"
- depends on NET_ETHERNET
- help
- Most ethernet controllers have MII transceiver either as an external
- or internal device. It is safe to say Y or M here even if your
- ethernet card lack MII.
-
source "drivers/net/arm/Kconfig"
config MACE
next reply other threads:[~2004-08-13 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 10:22 Adrian Bunk [this message]
2004-08-13 11:51 ` [2.6 patch] CONFIG_MII requires only CONFIG_NET Herbert Xu
2004-08-14 20:51 ` Adrian Bunk
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=20040813102202.GT13377@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.or \
--cc=linux-net@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 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.