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: ERROR: "gen_pool_virt_to_phys" [drivers/staging/vboxvideo/vboxvideo.ko] undefined!
Date: Sun, 30 Jul 2017 22:22:42 +0800 [thread overview]
Message-ID: <201707302240.aZcZoaSD%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
Hi Hans,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 0a07b238e5f488b459b6113a62e06b6aab017f71
commit: dd55d44f408419278c00887bfcb2261d0caae350 staging: vboxvideo: Add vboxvideo to drivers/staging
date: 13 days ago
config: x86_64-randconfig-a0-07302105 (attached as .config)
compiler: gcc-4.4 (Debian 4.4.7-8) 4.4.7
reproduce:
git checkout dd55d44f408419278c00887bfcb2261d0caae350
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
>> ERROR: "gen_pool_virt_to_phys" [drivers/staging/vboxvideo/vboxvideo.ko] undefined!
>> ERROR: "gen_pool_add_virt" [drivers/staging/vboxvideo/vboxvideo.ko] undefined!
>> ERROR: "gen_pool_destroy" [drivers/staging/vboxvideo/vboxvideo.ko] undefined!
>> ERROR: "gen_pool_dma_alloc" [drivers/staging/vboxvideo/vboxvideo.ko] undefined!
>> ERROR: "gen_pool_create" [drivers/staging/vboxvideo/vboxvideo.ko] undefined!
>> ERROR: "gen_pool_free" [drivers/staging/vboxvideo/vboxvideo.ko] undefined!
---
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: 27549 bytes --]
next reply other threads:[~2017-07-30 14:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-30 14:22 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-25 4:51 kbuild test robot
2017-07-25 8:51 ` Hans de Goede
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=201707302240.aZcZoaSD%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®