From: kernel test robot <lkp@intel.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Bjorn Andersson <andersson@kernel.org>
Subject: [linux-next:master 10281/11507] ERROR: modpost: "qcom_smem_is_available" [drivers/soc/qcom/ubwc_config.ko] undefined!
Date: Sat, 01 Aug 2026 07:29:15 +0800 [thread overview]
Message-ID: <202608010754.im6SvR4B-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 415606a7be939835db9b0d6b711887586646346d
commit: 1b445022d1d0ec7431b6f8fe0054ae8ccf33d60a [10281/11507] soc: qcom: ubwc: Get HBB from SMEM
config: arm64-randconfig-001-20260801 (https://download.01.org/0day-ci/archive/20260801/202608010754.im6SvR4B-lkp@intel.com/config)
compiler: clang version 21.1.8 (https://github.com/llvm/llvm-project 2078da43e25a4623cab2d0d60decddf709aaea28)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260801/202608010754.im6SvR4B-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/202608010754.im6SvR4B-lkp@intel.com/
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> ERROR: modpost: "qcom_smem_is_available" [drivers/soc/qcom/ubwc_config.ko] undefined!
>> ERROR: modpost: "qcom_smem_dram_get_hbb" [drivers/soc/qcom/ubwc_config.ko] undefined!
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-31 23:29 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=202608010754.im6SvR4B-lkp@intel.com \
--to=lkp@intel.com \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox