From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android12-5.4 5104/29950] hisi_hikey_usb.c:undefined reference to `usb_role_switch_unregister'
Date: Tue, 12 Dec 2023 03:25:45 +0800 [thread overview]
Message-ID: <202312120342.ZrhlMCPr-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android12-5.4
head: 1303f659c2b14b2e1b45dca5e98b79a2b818d4f6
commit: df2bbf3f35122d1d879aef65254ac09ede18e6f9 [5104/29950] ANDROID: misc: hisi_hikey_usb: Driver to support usb functionality of Hikey960
config: arm64-randconfig-003-20231205 (https://download.01.org/0day-ci/archive/20231212/202312120342.ZrhlMCPr-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231212/202312120342.ZrhlMCPr-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/202312120342.ZrhlMCPr-lkp@intel.com/
All errors (new ones prefixed by >>):
aarch64-linux-ld: warning: .tmp_vmlinux1 has a LOAD segment with RWX permissions
aarch64-linux-ld: drivers/misc/hisi_hikey_usb.o: in function `hisi_hikey_usb_remove':
>> hisi_hikey_usb.c:(.text+0x3c): undefined reference to `usb_role_switch_unregister'
hisi_hikey_usb.c:(.text+0x3c): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `usb_role_switch_unregister'
>> aarch64-linux-ld: hisi_hikey_usb.c:(.text+0x50): undefined reference to `usb_role_switch_put'
hisi_hikey_usb.c:(.text+0x50): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `usb_role_switch_put'
aarch64-linux-ld: drivers/misc/hisi_hikey_usb.o: in function `hub_usb_role_switch_get':
>> hisi_hikey_usb.c:(.text+0xb8): undefined reference to `usb_role_switch_get_role'
hisi_hikey_usb.c:(.text+0xb8): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `usb_role_switch_get_role'
aarch64-linux-ld: drivers/misc/hisi_hikey_usb.o: in function `hub_usb_role_switch_set':
>> hisi_hikey_usb.c:(.text+0x228): undefined reference to `usb_role_switch_set_role'
hisi_hikey_usb.c:(.text+0x228): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `usb_role_switch_set_role'
aarch64-linux-ld: drivers/misc/hisi_hikey_usb.o: in function `hisi_hikey_usb_probe':
>> hisi_hikey_usb.c:(.text+0x370): undefined reference to `usb_role_switch_get'
hisi_hikey_usb.c:(.text+0x370): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `usb_role_switch_get'
>> aarch64-linux-ld: hisi_hikey_usb.c:(.text+0x3cc): undefined reference to `usb_role_switch_register'
hisi_hikey_usb.c:(.text+0x3cc): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `usb_role_switch_register'
aarch64-linux-ld: hisi_hikey_usb.c:(.text+0x3f4): undefined reference to `usb_role_switch_put'
hisi_hikey_usb.c:(.text+0x3f4): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `usb_role_switch_put'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-11 19:26 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=202312120342.ZrhlMCPr-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--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.