The patch titled pcmcia/axnet_cs: make functions static has been removed from the -mm tree. Its filename was pcmcia-axnet_cs-make-functions-static.patch This patch was dropped because it was merged into mainline or a subsystem tree The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: pcmcia/axnet_cs: make functions static From: Richard Knutsson <ricknu-0@xxxxxxxxxxxxxx> Fixing: CHECK drivers/net/pcmcia/axnet_cs.c drivers/net/pcmcia/axnet_cs.c:994:5: warning: symbol 'ax_close' was not declared. Should it be static? drivers/net/pcmcia/axnet_cs.c:1017:6: warning: symbol 'ei_tx_timeout' was not declared. Should it be static? Signed-off-by: Richard Knutsson <ricknu-0@xxxxxxxxxxxxxx> Acked-by: Alan Cox <alan@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/net/pcmcia/axnet_cs.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff -puN drivers/net/pcmcia/axnet_cs.c~pcmcia-axnet_cs-make-functions-static drivers/net/pcmcia/axnet_cs.c --- a/drivers/net/pcmcia/axnet_cs.c~pcmcia-axnet_cs-make-functions-static +++ a/drivers/net/pcmcia/axnet_cs.c @@ -991,7 +991,7 @@ static int ax_open(struct net_device *de * * Opposite of ax_open(). Only used when "ifconfig <devname> down" is done. */ -int ax_close(struct net_device *dev) +static int ax_close(struct net_device *dev) { unsigned long flags; @@ -1014,7 +1014,7 @@ int ax_close(struct net_device *dev) * completed (or failed) - i.e. never posted a Tx related interrupt. */ -void ei_tx_timeout(struct net_device *dev) +static void ei_tx_timeout(struct net_device *dev) { long e8390_base = dev->base_addr; struct ei_device *ei_local = (struct ei_device *) netdev_priv(dev); _ Patches currently in -mm which might be from ricknu-0@xxxxxxxxxxxxxx are origin.patch reiserfs-complement-va_start-with-va_end.patch kernel-paramsc-remove-sparse-warning-different-signedness.patch - To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html