From: kbuild test robot <lkp@intel.com>
To: Matan Barak <matanb@mellanox.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Jason Gunthorpe <jgg@mellanox.com>,
Yishai Hadas <yishaih@mellanox.com>,
Leon Romanovsky <leonro@mellanox.com>
Subject: drivers/infiniband/hw/mlx5/main.c:4555: undefined reference to `uverbs_default_get_objects'
Date: Sun, 15 Apr 2018 09:55:02 +0800 [thread overview]
Message-ID: <201804150901.frf8aYYB%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1775 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 18b7fd1c93e5204355ddbf2608a097d64df81b88
commit: 8c84660bb437fe8692e6a2b4e85023ccb874a520 IB/mlx5: Initialize the parsing tree root without the help of uverbs
date: 10 days ago
config: x86_64-randconfig-s5-04150714 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
git checkout 8c84660bb437fe8692e6a2b4e85023ccb874a520
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/infiniband/hw/mlx5/main.o: In function `populate_specs_root':
>> drivers/infiniband/hw/mlx5/main.c:4555: undefined reference to `uverbs_default_get_objects'
>> drivers/infiniband/hw/mlx5/main.c:4559: undefined reference to `uverbs_alloc_spec_tree'
drivers/infiniband/hw/mlx5/main.o: In function `depopulate_specs_root':
>> drivers/infiniband/hw/mlx5/main.c:4566: undefined reference to `uverbs_free_spec_tree'
vim +4555 drivers/infiniband/hw/mlx5/main.c
4550
4551 #define NUM_TREES 0
4552 static int populate_specs_root(struct mlx5_ib_dev *dev)
4553 {
4554 const struct uverbs_object_tree_def *default_root[NUM_TREES + 1] = {
> 4555 uverbs_default_get_objects()};
4556 size_t num_trees = 1;
4557
4558 dev->ib_dev.specs_root =
> 4559 uverbs_alloc_spec_tree(num_trees, default_root);
4560
4561 return PTR_ERR_OR_ZERO(dev->ib_dev.specs_root);
4562 }
4563
4564 static void depopulate_specs_root(struct mlx5_ib_dev *dev)
4565 {
> 4566 uverbs_free_spec_tree(dev->ib_dev.specs_root);
4567 }
4568
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 35056 bytes --]
reply other threads:[~2018-04-15 1:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201804150901.frf8aYYB%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=jgg@mellanox.com \
--cc=kbuild-all@01.org \
--cc=leonro@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matanb@mellanox.com \
--cc=yishaih@mellanox.com \
/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
all inboxes | Powered by JetHome®