Thread (4 messages) 4 messages, 3 authors, 2018-09-07

Re: linux-next: build failure after merge of the bpf-next tree

From: Alexei Starovoitov <hidden>
Date: 2018-09-07 05:45:26
Also in: lkml, netdev

On Fri, Sep 07, 2018 at 07:21:05AM +0200, Björn Töpel wrote:
Den fre 7 sep. 2018 kl 02:23 skrev Alexei Starovoitov
[off-list ref]:
quoted
On Fri, Sep 07, 2018 at 10:19:23AM +1000, Stephen Rothwell wrote:
quoted
Hi all,

After merging the bpf-next tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:

ERROR: ".xsk_reuseq_swap" [drivers/net/ethernet/intel/i40e/i40e.ko] undefined!
ERROR: ".xsk_reuseq_free" [drivers/net/ethernet/intel/i40e/i40e.ko] undefined!
ERROR: ".xsk_reuseq_prepare" [drivers/net/ethernet/intel/i40e/i40e.ko] undefined

Caused by commit

  9654bd10da60 ("i40e: clean zero-copy XDP Rx ring on shutdown/reset")

CONFIG_XDP_SOCKETS is not set for this build.

I have used the version of the bfp-next tree from next-20180906 for today.
merge conflict and build error...
Bjorn, I'm thinking to toss the patches out of bpf-next and reapply
cleaned up version of the patches...
what do you think?
Yes, do that. I'll get back with a cleaned up v2.
Done.

Unfortunately during interactive rebase that removed your commits git didn't
preserve merge commits that came after yours,
so Jesper's and Yonghong's cover letters are not in the git history.
Yet all patches are in the same order.
Explicit revert with trail in the git history would have been worse.
patchworks + git isn't the most convenient workflow. sigh.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help