From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Leon Romanovsky <leon@kernel•org>, Doug Ledford <dledford@redhat•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: linux-next: build failure after merge of the rdma-leon tree
Date: Fri, 13 May 2016 10:08:07 +1000 [thread overview]
Message-ID: <20160513100807.05177f21@canb.auug.org.au> (raw)
Hi Leon,
After merging the rdma-leon tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
ERROR: ".rdma_addr_size" [drivers/infiniband/core/rdma_ucm.ko] undefined!
ERROR: ".rdma_addr_register_client" [drivers/infiniband/core/rdma_cm.ko] undefined!
ERROR: ".rdma_addr_size" [drivers/infiniband/core/rdma_cm.ko] undefined!
ERROR: ".rdma_addr_unregister_client" [drivers/infiniband/core/rdma_cm.ko] undefined!
ERROR: ".rdma_translate_ip" [drivers/infiniband/core/rdma_cm.ko] undefined!
ERROR: ".rdma_copy_addr" [drivers/infiniband/core/rdma_cm.ko] undefined!
ERROR: ".rdma_resolve_ip" [drivers/infiniband/core/rdma_cm.ko] undefined!
ERROR: ".rdma_addr_cancel" [drivers/infiniband/core/rdma_cm.ko] undefined!
ERROR: ".rdma_resolve_ip_route" [drivers/infiniband/core/ib_sa.ko] undefined!
ERROR: ".addr_init" [drivers/infiniband/core/ib_core.ko] undefined!
ERROR: ".rdma_addr_find_l2_eth_by_grh" [drivers/infiniband/core/ib_core.ko] undefined!
ERROR: ".addr_cleanup" [drivers/infiniband/core/ib_core.ko] undefined!
I don't know what has caused this, but the rdma-leon tree shares a lot
of patches (but not commits) with the rdma tree and so needs to be
cleaned up. Please sort out your work flow.
I have dropped the rdma-leon tree for today.
--
Cheers,
Stephen Rothwell
next reply other threads:[~2016-05-13 0:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 0:08 Stephen Rothwell [this message]
2016-05-13 0:33 ` linux-next: build failure after merge of the rdma-leon tree Stephen Rothwell
2016-05-13 17:09 ` Doug Ledford
-- strict thread matches above, loose matches on Subject: below --
2017-01-04 0:27 Stephen Rothwell
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=20160513100807.05177f21@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dledford@redhat$(echo .)com \
--cc=leon@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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