From: kernel test robot <[email protected]>
To: David Howells <[email protected]>
Cc: [email protected],
GNU/Weeb Mailing List <[email protected]>,
[email protected]
Subject: [ammarfaizi2-block:dhowells/linux-fs/netfs-lib 50/54] mips-linux-ld: fs/cifs/file.o:undefined reference to `netfs_invalidatepage'
Date: Wed, 9 Mar 2022 16:02:42 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
tree: https://github.com/ammarfaizi2/linux-block dhowells/linux-fs/netfs-lib
head: 2842e665b5eef341d10584ea2b8c4877b9141587
commit: a80918300e1cb9538bea4a225c7a45fe75f4678a [50/54] netfs: Provide invalidatepage and releasepage calls
config: mips-bmips_be_defconfig (https://download.01.org/0day-ci/archive/20220309/[email protected]/config)
compiler: mips-linux-gcc (GCC) 11.2.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
# https://github.com/ammarfaizi2/linux-block/commit/a80918300e1cb9538bea4a225c7a45fe75f4678a
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block dhowells/linux-fs/netfs-lib
git checkout a80918300e1cb9538bea4a225c7a45fe75f4678a
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=mips SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <[email protected]>
All errors (new ones prefixed by >>):
>> mips-linux-ld: fs/cifs/file.o:(.rodata+0xd4): undefined reference to `netfs_invalidatepage'
>> mips-linux-ld: fs/cifs/file.o:(.rodata+0xd8): undefined reference to `netfs_releasepage'
mips-linux-ld: fs/cifs/file.o:(.rodata+0x12c): undefined reference to `netfs_invalidatepage'
mips-linux-ld: fs/cifs/file.o:(.rodata+0x130): undefined reference to `netfs_releasepage'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/[email protected]
reply other threads:[~2022-03-09 8:03 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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