From: kernel test robot <lkp@intel.com>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org
Subject: [martinetd:9p-next 11/13] ERROR: modpost: "p9_fid_put" [fs/9p/9p.ko] undefined!
Date: Sun, 12 Jun 2022 20:18:10 +0800 [thread overview]
Message-ID: <202206122057.RBESqurT-lkp@intel.com> (raw)
tree: https://github.com/martinetd/linux.git 9p-next
head: 9bb9cdaaa704d542e2fca976fa17f80f769fc341
commit: 6334def2e0b55439c8d86b769b23c03fb79f8ec4 [11/13] 9p fid refcount: add p9_fid_get/put wrappers
config: i386-randconfig-a015 (https://download.01.org/0day-ci/archive/20220612/202206122057.RBESqurT-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 6466c9abf3674bade1f6ee859f24ebc7aaf9cd88)
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
# https://github.com/martinetd/linux/commit/6334def2e0b55439c8d86b769b23c03fb79f8ec4
git remote add martinetd https://github.com/martinetd/linux.git
git fetch --no-tags martinetd 9p-next
git checkout 6334def2e0b55439c8d86b769b23c03fb79f8ec4
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> ERROR: modpost: "p9_fid_put" [fs/9p/9p.ko] undefined!
>> ERROR: modpost: "p9_fid_get" [fs/9p/9p.ko] undefined!
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-06-12 12:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 12:18 kernel test robot [this message]
2022-06-12 12:23 ` [martinetd:9p-next 11/13] ERROR: modpost: "p9_fid_put" [fs/9p/9p.ko] undefined! Dominique Martinet
2022-06-12 12:23 ` Dominique Martinet
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=202206122057.RBESqurT-lkp@intel.com \
--to=lkp@intel.com \
--cc=asmadeus@codewreck.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
/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.