From: kbuild test robot <fengguang.wu@intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Michael Thayer <michael.thayer@oracle.com>
Subject: vbox_hgsmi.c:undefined reference to `gen_pool_dma_alloc'
Date: Tue, 25 Jul 2017 17:11:32 +0800 [thread overview]
Message-ID: <201707251730.KX4romcO%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1598 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 520eccdfe187591a51ea9ab4c1a024ae4d0f68d9
commit: dd55d44f408419278c00887bfcb2261d0caae350 staging: vboxvideo: Add vboxvideo to drivers/staging
date: 8 days ago
config: x86_64-randconfig-s4-07251602 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
git checkout dd55d44f408419278c00887bfcb2261d0caae350
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/staging/vboxvideo/vbox_hgsmi.o: In function `hgsmi_buffer_alloc':
>> vbox_hgsmi.c:(.text+0x48): undefined reference to `gen_pool_dma_alloc'
drivers/staging/vboxvideo/vbox_hgsmi.o: In function `hgsmi_buffer_free':
>> vbox_hgsmi.c:(.text+0xe3): undefined reference to `gen_pool_free'
drivers/staging/vboxvideo/vbox_hgsmi.o: In function `hgsmi_buffer_submit':
>> vbox_hgsmi.c:(.text+0xf2): undefined reference to `gen_pool_virt_to_phys'
drivers/staging/vboxvideo/vbox_main.o: In function `vbox_hw_fini':
>> vbox_main.c:(.text+0xf9): undefined reference to `gen_pool_destroy'
drivers/staging/vboxvideo/vbox_main.o: In function `vbox_driver_load':
>> vbox_main.c:(.text+0x487): undefined reference to `gen_pool_create'
>> vbox_main.c:(.text+0x4b2): undefined reference to `gen_pool_add_virt'
vbox_main.c:(.text+0x614): undefined reference to `gen_pool_destroy'
---
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: 25099 bytes --]
reply other threads:[~2017-07-25 9:13 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=201707251730.KX4romcO%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.thayer@oracle.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®