From: Kumar Gala <galak@kernel•crashing.org>
To: subrata@linux•vnet.ibm.com
Cc: Linuxppc-dev <Linuxppc-dev@ozlabs•org>,
linux-next <linux-next@vger•kernel.org>,
linux-kernel <linux-kernel@vger•kernel.org>,
linux-net@vger•kernel.org, Greg KH <greg@kroah•com>,
sachinp <sachinp@linux•vnet.ibm.com>,
Stephen Rothwell <sfr@canb•auug.org.au>
Subject: Re: [BUILD FAILURE 04] Next April 9 : PPC64 randconfig [drivers/net/ibm_newemac/core.c]
Date: Thu, 9 Apr 2009 09:28:23 -0500 [thread overview]
Message-ID: <BE92FB74-1784-414B-B27F-8329185EB3AE@kernel.crashing.org> (raw)
In-Reply-To: <1239285152.5188.66.camel@subratamodak.linux.ibm.com>
On Apr 9, 2009, at 8:52 AM, Subrata Modak wrote:
> Observed the following build error:
>
> CC drivers/net/ibm_newemac/core.o
> drivers/net/ibm_newemac/core.c: In function ‘emac_probe’:
> drivers/net/ibm_newemac/core.c:2831: error: ‘struct net_device’ has no
> member named ‘open’
> drivers/net/ibm_newemac/core.c:2834: error: ‘struct net_device’ has no
> member named ‘tx_timeout’
> drivers/net/ibm_newemac/core.c:2836: error: ‘struct net_device’ has no
> member named ‘stop’
> drivers/net/ibm_newemac/core.c:2837: error: ‘struct net_device’ has no
> member named ‘get_stats’
> drivers/net/ibm_newemac/core.c:2838: error: ‘struct net_device’ has no
> member named ‘set_multicast_list’
> drivers/net/ibm_newemac/core.c:2839: error: ‘struct net_device’ has no
> member named ‘do_ioctl’
> drivers/net/ibm_newemac/core.c:2841: error: ‘struct net_device’ has no
> member named ‘hard_start_xmit’
> drivers/net/ibm_newemac/core.c:2842: error: ‘struct net_device’ has no
> member named ‘change_mtu’
> drivers/net/ibm_newemac/core.c:2845: error: ‘struct net_device’ has no
> member named ‘hard_start_xmit’
> make[3]: *** [drivers/net/ibm_newemac/core.o] Error 1
> make[2]: *** [drivers/net/ibm_newemac] Error 2
> make[1]: *** [drivers/net] Error 2
> make: *** [drivers] Error 2
>
> Regards--
> Subrata
>
> <randconfig4-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
next prev parent reply other threads:[~2009-04-09 14:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 13:52 [BUILD FAILURE 04] Next April 9 : PPC64 randconfig [drivers/net/ibm_newemac/core.c] Subrata Modak
2009-04-09 13:57 ` [BUILD FAILURE 05] Next April 9 : PPC64 randconfig [drivers/net/wan/wanxlfw.inc] Subrata Modak
2009-04-09 14:51 ` Geert Uytterhoeven
2009-04-09 15:24 ` [BUILD FAILURE 06] Next April 9 : PPC64 randconfig [drivers/usb/musb/musb_core.c] Subrata Modak
2009-04-09 15:24 ` [BUILD FAILURE 07] Next April 9 : PPC64 randconfig [drivers/scsi/aha1542.o] Subrata Modak
2009-04-09 15:28 ` [BUILD FAILURE 08] Next April 9 : PPC64 randconfig [drivers/net/pasemi_mac_driver.ko] Subrata Modak
2009-04-09 15:34 ` [BUILD FAILURE 09] Next April 9 : PPC64 randconfig [drivers/char/hvcs.ko] Subrata Modak
2009-04-09 14:28 ` Kumar Gala [this message]
2009-04-09 14:31 ` [BUILD FAILURE 04] Next April 9 : PPC64 randconfig [drivers/net/ibm_newemac/core.c] Josh Boyer
2009-04-10 1:56 ` Alexander Beregalov
2009-04-11 9:44 ` David Miller
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=BE92FB74-1784-414B-B27F-8329185EB3AE@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