The patch titled
     powerpc: fs_enet: select PHYLIB as the driver needs it.
has been added to the -mm tree.  Its filename is
     powerpc-fs_enet-select-phylib-as-the-driver-needs-it.patch

*** Remember to use Documentation/SubmitChecklist when testing your code ***

See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this

------------------------------------------------------
Subject: powerpc: fs_enet: select PHYLIB as the driver needs it.
From: Jochen Friedrich <[EMAIL PROTECTED]>

Add a select PHYLIB to config FS_ENET as the driver uses functions of
libphy.

LD      .tmp_vmlinux1
drivers/built-in.o: In function `fs_ioctl':
drivers/net/fs_enet/fs_enet-main.c:952: undefined reference to `phy_mii_ioctl'
[...]
make: *** [.tmp_vmlinux1] Error 1

Signed-off-by: Jochen Friedrich <[EMAIL PROTECTED]>
Cc: Paul Mackerras <[EMAIL PROTECTED]>
Cc: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
Cc: Jeff Garzik <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---

 drivers/net/fs_enet/Kconfig |    7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff -puN 
drivers/net/fs_enet/Kconfig~powerpc-fs_enet-select-phylib-as-the-driver-needs-it
 drivers/net/fs_enet/Kconfig
--- 
a/drivers/net/fs_enet/Kconfig~powerpc-fs_enet-select-phylib-as-the-driver-needs-it
+++ a/drivers/net/fs_enet/Kconfig
@@ -1,7 +1,8 @@
 config FS_ENET
-       tristate "Freescale Ethernet Driver"
-       depends on CPM1 || CPM2
-       select MII
+       tristate "Freescale Ethernet Driver"
+       depends on CPM1 || CPM2
+       select MII
+       select PHYLIB
 
 config FS_ENET_HAS_SCC
        bool "Chip has an SCC usable for ethernet"
_

Patches currently in -mm which might be from [EMAIL PROTECTED] are

powerpc-kill-non-existent-symbols-from-ksyms-and-commproch.patch
powerpc-fs_enet-select-phylib-as-the-driver-needs-it.patch
powerpc-fix-typo-ifdef-ifndef.patch

-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to