From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [peterz-queue:x86/static_call 17/18] ERROR: modpost: "__tracepoint_iter_br_fdb_external_learn_add" undefined!
Date: Sat, 20 Jun 2020 12:27:06 +0800 [thread overview]
Message-ID: <202006201204.PoTwOUef%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1568 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git x86/static_call
head: 4e42463b16b84ae3acf41b3987e89e1d44a70eff
commit: 321d008f4bb9e8f9425f4d3fc3aca6755f3110f7 [17/18] tracepoint: Optimize using static_call()
config: mips-randconfig-r004-20200619 (attached as .config)
compiler: mipsel-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 checkout 321d008f4bb9e8f9425f4d3fc3aca6755f3110f7
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=mips
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: "__tracepoint_iter_br_fdb_external_learn_add" [net/bridge/bridge.ko] undefined!
>> ERROR: modpost: "__tracepoint_iter_br_fdb_add" [net/bridge/bridge.ko] undefined!
>> ERROR: modpost: "__tracepoint_iter_fdb_delete" [net/bridge/bridge.ko] undefined!
>> ERROR: modpost: "__tracepoint_iter_br_fdb_update" [net/bridge/bridge.ko] undefined!
>> ERROR: modpost: "__tracepoint_iter_tcp_send_reset" [net/ipv6/ipv6.ko] undefined!
>> ERROR: modpost: "__tracepoint_iter_dma_fence_emit" [drivers/gpu/drm/virtio/virtio-gpu.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: 25077 bytes --]
reply other threads:[~2020-06-20 4:27 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=202006201204.PoTwOUef%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.