From: kernel test robot <lkp@intel.com>
To: Piyush Mehta <piyush.mehta@amd.com>
Cc: oe-kbuild-all@lists.linux.dev, git@amd.com,
Michal Simek <monstr@monstr.eu>,
Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>
Subject: [xilinx-xlnx:xlnx_rebase_v6.6_LTS_2024.1_update 643/1001] core.c:undefined reference to `ulpi_write'
Date: Fri, 27 Sep 2024 20:18:12 +0800 [thread overview]
Message-ID: <202409272042.PBj2fTY4-lkp@intel.com> (raw)
tree: https://github.com/Xilinx/linux-xlnx xlnx_rebase_v6.6_LTS_2024.1_update
head: 5365c13a86998da06d845c918f849b30b8735538
commit: aca8761729017fb7d788d9c07e6c50b169b425f6 [643/1001] usb: dwc3: core: Add support for disabling vbus when suspended
config: loongarch-randconfig-001-20240927 (https://download.01.org/0day-ci/archive/20240927/202409272042.PBj2fTY4-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240927/202409272042.PBj2fTY4-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/202409272042.PBj2fTY4-lkp@intel.com/
All errors (new ones prefixed by >>):
loongarch64-linux-ld: drivers/usb/dwc3/core.o: in function `.LVL441':
>> core.c:(.text+0x1e04): undefined reference to `ulpi_write'
loongarch64-linux-ld: drivers/usb/dwc3/core.o: in function `.LVL497':
core.c:(.text+0x202c): undefined reference to `dwc3_gadget_exit_hibernation'
loongarch64-linux-ld: drivers/usb/dwc3/core.o: in function `.LVL544':
core.c:(.text+0x21ec): undefined reference to `dwc3_gadget_exit_hibernation'
loongarch64-linux-ld: drivers/usb/dwc3/core.o: in function `.LVL1045':
core.c:(.text+0x36b4): undefined reference to `ulpi_write'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-09-27 12:19 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=202409272042.PBj2fTY4-lkp@intel.com \
--to=lkp@intel.com \
--cc=git@amd.com \
--cc=monstr@monstr.eu \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=piyush.mehta@amd.com \
--cc=radhey.shyam.pandey@amd.com \
/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.