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 =91fs_enet_probe=92:
> drivers/net/fs_enet/fs_enet-main.c:1096: error: =91struct net_device=92 =
=20
> has
> no member named =91open=92
> drivers/net/fs_enet/fs_enet-main.c:1097: error: =91struct net_device=92 =
=20
> has
> no member named =91hard_start_xmit=92
> drivers/net/fs_enet/fs_enet-main.c:1098: error: =91struct net_device=92 =
=20
> has
> no member named =91tx_timeout=92
> drivers/net/fs_enet/fs_enet-main.c:1100: error: =91struct net_device=92 =
=20
> has
> no member named =91stop=92
> drivers/net/fs_enet/fs_enet-main.c:1101: error: =91struct net_device=92 =
=20
> has
> no member named =91get_stats=92
> drivers/net/fs_enet/fs_enet-main.c:1102: error: =91struct net_device=92 =
=20
> has
> no member named =91set_multicast_list=92
> drivers/net/fs_enet/fs_enet-main.c:1111: error: =91struct net_device=92 =
=20
> has
> no member named =91do_ioctl=92
> 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 =20=
this driver to build. I've asked the netdev guys about either fixing =20=
the driver or adding the proper thing to Kconfig to select =20
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.crashing.org \
--cc=Linuxppc-dev@ozlabs.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sachinp@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=subrata@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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