From: Kumar Gala <galak@kernel•crashing.org>
To: subrata@linux•vnet.ibm.com
Cc: sachinp <sachinp@linux•vnet.ibm.com>,
Stephen Rothwell <sfr@canb•auug.org.au>, Greg KH <greg@kroah•com>,
linux-kernel <linux-kernel@vger•kernel.org>,
Linuxppc-dev <Linuxppc-dev@ozlabs•org>,
linux-next <linux-next@vger•kernel.org>,
linux-net@vger•kernel.org
Subject: Re: [BUILD FAILURE 01] Next April 9 : PPC64 randconfig [drivers/net/fs_enet/fs_enet-main.c]
Date: Thu, 9 Apr 2009 09:28:13 -0500 [thread overview]
Message-ID: <21BA9149-6948-42C0-9F76-033185BB5296@kernel.crashing.org> (raw)
In-Reply-To: <1239285022.5188.63.camel@subratamodak.linux.ibm.com>
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
prev parent reply other threads:[~2009-04-09 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 13:50 [BUILD FAILURE 01] Next April 9 : PPC64 randconfig [drivers/net/fs_enet/fs_enet-main.c] Subrata Modak
2009-04-09 14:28 ` Kumar Gala [this message]
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=21BA9149-6948-42C0-9F76-033185BB5296@kernel.crashing.org \
--to=galak@kernel$(echo .)crashing.org \
--cc=Linuxppc-dev@ozlabs$(echo .)org \
--cc=greg@kroah$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-net@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sachinp@linux$(echo .)vnet.ibm.com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=subrata@linux$(echo .)vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox