From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [drm-drm-misc:for-linux-next 3/3] ERROR: modpost: "dma_resv_reset_shared_max" [drivers/gpu/drm/etnaviv/etnaviv.ko] undefined!
Date: Fri, 04 Jun 2021 23:26:22 +0800 [thread overview]
Message-ID: <202106042309.5FVo72K6-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1533 bytes --]
tree: git://anongit.freedesktop.org/drm/drm-misc for-linux-next
head: 0c6b522abc2a592468992780babd3c3629c7ceac
commit: 0c6b522abc2a592468992780babd3c3629c7ceac [3/3] dma-buf: cleanup dma-resv shared fence debugging a bit v2
config: microblaze-randconfig-r013-20210604 (attached as .config)
compiler: microblaze-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git remote add drm-drm-misc git://anongit.freedesktop.org/drm/drm-misc
git fetch --no-tags drm-drm-misc for-linux-next
git checkout 0c6b522abc2a592468992780babd3c3629c7ceac
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=microblaze
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> ERROR: modpost: "dma_resv_reset_shared_max" [drivers/gpu/drm/etnaviv/etnaviv.ko] undefined!
>> ERROR: modpost: "dma_resv_reset_shared_max" [drivers/gpu/drm/virtio/virtio-gpu.ko] undefined!
>> ERROR: modpost: "dma_resv_reset_shared_max" [drivers/gpu/drm/vgem/vgem.ko] undefined!
>> ERROR: modpost: "dma_resv_reset_shared_max" [drivers/gpu/drm/drm.ko] undefined!
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 30040 bytes --]
reply other threads:[~2021-06-04 15:26 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=202106042309.5FVo72K6-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.