[patch] 2.6.8-rc1-mm1: 8139too: uninline rtl8139_start_thread

From: Adrian Bunk
Date: Wed Jul 14 2004 - 15:43:36 EST


On Wed, Jul 14, 2004 at 10:29:18PM +0200, Dominik Karall wrote:
> On Wednesday 14 July 2004 03:25, Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.8-rc1/2.6
> >.8-rc1-mm1/
>
> CC [M] drivers/net/8139too.o
> drivers/net/8139too.c: In function `rtl8139_open':
> drivers/net/8139too.c:616: nicht implementiert: >>inline<< beim Aufruf von
> >>rtl8139_start_thread<< gescheitert: function body not available
> drivers/net/8139too.c:1362: nicht implementiert: von hier aufgerufen
> make[3]: *** [drivers/net/8139too.o] Fehler 1
> make[2]: *** [drivers/net] Fehler 2
> make[1]: *** [drivers] Fehler 2
> make[1]: Verlasse Verzeichnis »/usr/src/linux-2.6.6«
> make: *** [stamp-build] Fehler 2
>
> gcc 3.4

I should be fast at going through my gcc 3.4 TODO list...

Fix below.

> greets
> dominik

cu
Adrian


<-- snip -->


uninline rtl8139_start_thread in drivers/net/8139too.c .


Signed-off-by: Adrian Bunk <bunk@xxxxxxxxx>

--- linux-2.6.7-mm6-full-gcc3.4/drivers/net/8139too.c.old 2004-07-09 00:49:24.000000000 +0200
+++ linux-2.6.7-mm6-full-gcc3.4/drivers/net/8139too.c 2004-07-09 00:52:55.000000000 +0200
@@ -613,7 +613,7 @@
static int mdio_read (struct net_device *dev, int phy_id, int location);
static void mdio_write (struct net_device *dev, int phy_id, int location,
int val);
-static inline void rtl8139_start_thread(struct net_device *dev);
+static void rtl8139_start_thread(struct net_device *dev);
static void rtl8139_tx_timeout (struct net_device *dev);
static void rtl8139_init_ring (struct net_device *dev);
static int rtl8139_start_xmit (struct sk_buff *skb,
@@ -1643,7 +1643,7 @@
complete_and_exit (&tp->thr_exited, 0);
}

-static inline void rtl8139_start_thread(struct net_device *dev)
+static void rtl8139_start_thread(struct net_device *dev)
{
struct rtl8139_private *tp = dev->priv;

-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html