[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <21BA9149-6948-42C0-9F76-033185BB5296@kernel.crashing.org>
Date: Thu, 9 Apr 2009 09:28:13 -0500
From: Kumar Gala <galak@...nel.crashing.org>
To: subrata@...ux.vnet.ibm.com
Cc: Linuxppc-dev <Linuxppc-dev@...abs.org>,
linux-next <linux-next@...r.kernel.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
sachinp <sachinp@...ux.vnet.ibm.com>, linux-net@...r.kernel.org,
Greg KH <greg@...ah.com>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [BUILD FAILURE 01] Next April 9 : PPC64 randconfig [drivers/net/fs_enet/fs_enet-main.c]
On Apr 9, 2009, at 8:50 AM, Subrata Modak wrote:
> Observed the following build error:
>
> drivers/net/fs_enet/fs_enet-main.c: In function ‘fs_enet_probe’:
> drivers/net/fs_enet/fs_enet-main.c:1096: error: ‘struct net_device’
> has
> no member named ‘open’
> drivers/net/fs_enet/fs_enet-main.c:1097: error: ‘struct net_device’
> has
> no member named ‘hard_start_xmit’
> drivers/net/fs_enet/fs_enet-main.c:1098: error: ‘struct net_device’
> has
> no member named ‘tx_timeout’
> drivers/net/fs_enet/fs_enet-main.c:1100: error: ‘struct net_device’
> has
> no member named ‘stop’
> drivers/net/fs_enet/fs_enet-main.c:1101: error: ‘struct net_device’
> has
> no member named ‘get_stats’
> drivers/net/fs_enet/fs_enet-main.c:1102: error: ‘struct net_device’
> has
> no member named ‘set_multicast_list’
> drivers/net/fs_enet/fs_enet-main.c:1111: error: ‘struct net_device’
> has
> no member named ‘do_ioctl’
> make[3]: *** [drivers/net/fs_enet/fs_enet-main.o] Error 1
> make[2]: *** [drivers/net/fs_enet] Error 2
> make[1]: *** [drivers/net] Error 2
> make: *** [drivers] Error 2
>
> Regards--
> Subrata
>
> <randconfig1-ppc64-next20090409.txt>
This is because CONFIG_COMPAT_NET_DEV_OPS isnt set and needs to be for
this driver to build. I've asked the netdev guys about either fixing
the driver or adding the proper thing to Kconfig to select
CONFIG_COMPAT_NET_DEV_OPS.
- k--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists