randconfig build error with next-20140502, in drivers/net/hyperv/netvsc_drv.c

KY Srinivasan kys at microsoft.com
Fri May 2 14:59:58 UTC 2014



> -----Original Message-----
> From: Haiyang Zhang
> Sent: Friday, May 2, 2014 7:42 AM
> To: Jim Davis; Stephen Rothwell; linux-next; linux-kernel; KY Srinivasan;
> devel at linuxdriverproject.org; netdev
> Subject: RE: randconfig build error with next-20140502, in
> drivers/net/hyperv/netvsc_drv.c
> 
> 
> 
> > -----Original Message-----
> > From: Jim Davis [mailto:jim.epost at gmail.com]
> > Sent: Friday, May 2, 2014 9:56 AM
> > To: Stephen Rothwell; linux-next; linux-kernel; KY Srinivasan; Haiyang
> > Zhang; devel at linuxdriverproject.org; netdev
> > Subject: randconfig build error with next-20140502, in
> > drivers/net/hyperv/netvsc_drv.c
> >
> > Building with the attached random configuration file,
> >
> > drivers/net/hyperv/netvsc_drv.c: In function ‘netvsc_recv_callback’:
> > drivers/net/hyperv/netvsc_drv.c:648:11: error: ‘struct net_device’ has
> > no member  named ‘real_num_rx_queues’
> >         net->real_num_rx_queues);
> >            ^
> > In file included from drivers/net/hyperv/netvsc_drv.c:26:0:
> > drivers/net/hyperv/netvsc_drv.c: In function ‘netvsc_probe’:
> > drivers/net/hyperv/netvsc_drv.c:832:32: error: ‘struct net_device’ has
> > no member named ‘real_num_rx_queues’
> >     net->real_num_tx_queues, net->real_num_rx_queues);
> >                                 ^
> > include/linux/device.h:1080:58: note: in definition of macro ‘dev_info’
> >  #define dev_info(dev, fmt, arg...) _dev_info(dev, fmt, ##arg)
> >                                                           ^
> > make[3]: *** [drivers/net/hyperv/netvsc_drv.o] Error 1
> 
> real_num_rx_queues is defined in "include/linux/netdevice.h":
> It requires CONFIG_SYSFS flag, which is enabled by default, but not set in
> your config file.
> 
> Could you use default config and add hyperv drivers, then try again?

Haiyang,

That is the point - the code must compile correctly for all possible configurations.
You will want to protect the dependencies appropriately.

K. Y
> 
> Thanks,
> - Haiyang
> 



More information about the devel mailing list