From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Alexei Starovoitov <ast@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
brouer@redhat.com
Subject: Re: Build failure in -next due to 'xdp: generic XDP handling of xdp_rxq_info'
Date: Tue, 9 Jan 2018 23:37:42 +0100 [thread overview]
Message-ID: <20180109233742.101bfa1a@redhat.com> (raw)
In-Reply-To: <20180109190147.GA28680@roeck-us.net>
On Tue, 9 Jan 2018 11:01:47 -0800
Guenter Roeck <linux@roeck-us.net> wrote:
> Hi,
>
> commit e817f85652c ("xdp: generic XDP handling of xdp_rxq_info") results in
> the following error when building m68k:m5208evb_defconfig in -next.
>
> net/core/dev.c: In function 'netif_get_rxqueue':
> net/core/dev.c:3926:15: error: 'struct net_device' has no member named '_rx'
> net/core/dev.c:3931:28: error:
> 'struct net_device' has no member named 'real_num_rx_queues'
>
> net/core/dev.c: In function 'netif_alloc_rx_queues':
> net/core/dev.c:7633:29: error:
> 'struct net_device' has no member named 'num_rx_queues'
>
> [ and so on ]
Hi Guenter,
This is caused by CONFIG_SYSFS is not set in your config. I'm
preparing a patch... can I ask you to test it, as I have a hard time
disabling on my X86_64 system.
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2018-01-09 22:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 19:01 Build failure in -next due to 'xdp: generic XDP handling of xdp_rxq_info' Guenter Roeck
2018-01-09 22:37 ` Jesper Dangaard Brouer [this message]
2018-01-09 22:42 ` [net-next PATCH] net: fix xdp_rxq_info build issue when CONFIG_SYSFS is not set Jesper Dangaard Brouer
2018-01-09 22:57 ` Guenter Roeck
2018-01-10 20:41 ` 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=20180109233742.101bfa1a@redhat.com \
--to=brouer@redhat.com \
--cc=ast@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).