From: kernel test robot <lkp@intel.com>
To: Jens Wiklander <jens.wiklander@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Tomas Winkler <tomas.winkler@intel.com>,
Alexander Usyskin <alexander.usyskin@intel.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: [linux-next:master 5982/8126] ld.lld: error: undefined symbol: rpmb_dev_register
Date: Mon, 2 Sep 2024 14:28:21 +0800 [thread overview]
Message-ID: <202409021448.RSvcBPzt-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 985bf40edf4343dcb04c33f58b40b4a85c1776d4
commit: 7852028a35f03e04c9cdc92fd26894cca4a8a4de [5982/8126] mmc: block: register RPMB partition with the RPMB subsystem
config: x86_64-randconfig-101-20240902 (https://download.01.org/0day-ci/archive/20240902/202409021448.RSvcBPzt-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240902/202409021448.RSvcBPzt-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/202409021448.RSvcBPzt-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: rpmb_dev_register
>>> referenced by block.c:3229 (drivers/mmc/core/block.c:3229)
>>> vmlinux.o:(mmc_blk_probe)
--
>> ld.lld: error: undefined symbol: rpmb_dev_unregister
>>> referenced by block.c:2748 (drivers/mmc/core/block.c:2748)
>>> vmlinux.o:(mmc_blk_rpmb_device_release)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-09-02 6:28 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=202409021448.RSvcBPzt-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexander.usyskin@intel.com \
--cc=jens.wiklander@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tomas.winkler@intel.com \
--cc=ulf.hansson@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox