RE: randconfig build error with next-20140502, in drivers/net/hyperv/netvsc_drv.c
From: Haiyang Zhang
Date: Fri May 02 2014 - 11:26:12 EST
> -----Original Message-----
> From: KY Srinivasan
> Sent: Friday, May 2, 2014 11:00 AM
> To: Haiyang Zhang; Jim Davis; Stephen Rothwell; linux-next; linux-kernel;
> devel@xxxxxxxxxxxxxxxxxxxxxx; netdev
> Subject: RE: randconfig build error with next-20140502, in
> drivers/net/hyperv/netvsc_drv.c
>
>
>
> > -----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@xxxxxxxxxxxxxxxxxxxxxx; netdev
> > Subject: RE: randconfig build error with next-20140502, in
> > drivers/net/hyperv/netvsc_drv.c
> >
> >
> >
> > > -----Original Message-----
> > > From: Jim Davis [mailto:jim.epost@xxxxxxxxx]
> > > Sent: Friday, May 2, 2014 9:56 AM
> > > To: Stephen Rothwell; linux-next; linux-kernel; KY Srinivasan;
> Haiyang
> > > Zhang; devel@xxxxxxxxxxxxxxxxxxxxxx; 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.
>
OK, I'll look into this.
Thanks,
- Haiyang