From: kernel test robot <lkp@intel.com>
To: Wesley Cheng <wcheng@codeaurora.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Steev Klimaszewski <steev@kali.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: [steev:linux-v5.19.0 69/198] ERROR: modpost: "typec_switch_get_drvdata" [drivers/phy/qualcomm/phy-qcom-qmp.ko] undefined!
Date: Wed, 3 Aug 2022 09:16:12 +0800 [thread overview]
Message-ID: <202208030957.PlLylDr3-lkp@intel.com> (raw)
tree: https://github.com/steev/linux linux-v5.19.0
head: a4510d0cef54eda304739679db13f1f17abe4125
commit: 52c2355f918241ce43caf2fbceb8aff380038507 [69/198] phy: qcom-qmp: Register as a typec switch for orientation detection
config: openrisc-randconfig-r023-20220801 (https://download.01.org/0day-ci/archive/20220803/202208030957.PlLylDr3-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 12.1.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/steev/linux/commit/52c2355f918241ce43caf2fbceb8aff380038507
git remote add steev https://github.com/steev/linux
git fetch --no-tags steev linux-v5.19.0
git checkout 52c2355f918241ce43caf2fbceb8aff380038507
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=openrisc 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: "typec_switch_get_drvdata" [drivers/phy/qualcomm/phy-qcom-qmp.ko] undefined!
>> ERROR: modpost: "typec_switch_register" [drivers/phy/qualcomm/phy-qcom-qmp.ko] undefined!
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-08-03 1:16 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=202208030957.PlLylDr3-lkp@intel.com \
--to=lkp@intel.com \
--cc=bjorn.andersson@linaro.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steev@kali.org \
--cc=wcheng@codeaurora.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
all inboxes | Powered by JetHome®