From: kernel test robot <lkp@intel.com>
To: Christian Brauner <brauner@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Christian Brauner <christianvanbrauner@gmail.com>
Subject: [brauner-vfs:b4/vfs-super-mtd 51/51] ld.lld: error: undefined symbol: sget_dev
Date: Wed, 30 Aug 2023 03:33:04 +0800 [thread overview]
Message-ID: <202308300300.vRFhalwF-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git b4/vfs-super-mtd
head: a115996e417a9245d3f9974b94f649479ad76f99
commit: c73c565bd77f3823dffaaca4cc2887889a48c4f9 [51/51] mtd: key superblock by device number
config: arm-randconfig-r011-20230830 (https://download.01.org/0day-ci/archive/20230830/202308300300.vRFhalwF-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230830/202308300300.vRFhalwF-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202308300300.vRFhalwF-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: sget_dev
>>> referenced by mtdsuper.c:33 (drivers/mtd/mtdsuper.c:33)
>>> drivers/mtd/mtdsuper.o:(mtd_get_sb) in archive vmlinux.a
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-08-29 19:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 19:33 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-29 22:09 [brauner-vfs:b4/vfs-super-mtd 51/51] ld.lld: error: undefined symbol: sget_dev kernel test robot
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=202308300300.vRFhalwF-lkp@intel.com \
--to=lkp@intel.com \
--cc=brauner@kernel.org \
--cc=christianvanbrauner@gmail.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@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.