Thread (7 messages) 7 messages, 3 authors, 2016-08-09

Re: linux-next: build failure after merge of Linus' tree

From: Doug Ledford <hidden>
Date: 2016-08-08 23:31:12
Also in: lkml

On 8/8/2016 5:53 PM, Stephen Rothwell wrote:
Hi Doug,

On Mon, 8 Aug 2016 11:37:33 -0400 Doug Ledford [off-list ref] wrote:
quoted
On 8/7/2016 9:58 PM, Stephen Rothwell wrote:
quoted
With Linus' tree, today's linux-next build (powerpc allyesconfig) failed
like this:

drivers/infiniband/sw/built-in.o:(.opd+0x1698): multiple definition of `copy_data'
drivers/infiniband/hw/built-in.o:(.opd+0xe5f8): first defined here
drivers/infiniband/sw/built-in.o:(.opd+0x1320): multiple definition of `rxe_av_from_attr'
drivers/infiniband/hw/built-in.o:(.opd+0xe280): first defined here  
This looks very suspicious.  I think you are picking up two copies of
the rxe code.  One from Linus tree and one from probably Leon's tree.
Actually the second copy is from your tree
(git://git.kernel.org/pub/scm/linux/kernel/git/dledford/rdma.git#for-next),
Leon's trees are empty (relative to Linus' tree).  I guess when you
rebased and squashed things, you forgot to reset your for-next tag, so
I got the old version of your tree as well as the rebased version via
Linus' tree.
Doh!  My apologies, that would certainly explain it.  I'll reset my
for-next tag.


-- 
Doug Ledford [off-list ref]
    GPG Key ID: 0E572FDD

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help