From: kernel test robot <lkp@intel.com>
To: Piyush Mehta <piyush.mehta@xilinx.com>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
linux-arm-kernel@lists.infradead.org,
Michal Simek <monstr@monstr.eu>,
Anurag Kumar Vulisha <anurag.kumar.vulisha@xilinx.com>
Subject: [xlnx:xlnx_rebase_v5.4 906/1762] ld.lld: error: duplicate symbol: dwc3_simple_check_quirks
Date: Wed, 16 Jun 2021 15:13:24 +0800 [thread overview]
Message-ID: <202106161520.HWJ1QlIQ-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2404 bytes --]
Hi Piyush,
FYI, the error/warning still remains.
tree: https://github.com/Xilinx/linux-xlnx xlnx_rebase_v5.4
head: d128303e4c53bcf7775c46771bf64c71596f3303
commit: 782658c51bbcd85a39a5d9a51b57224f185d7670 [906/1762] usb: dwc3: Correct errors when dwc3 loaded as module
config: x86_64-randconfig-a014-20210615 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project 64720f57bea6a6bf033feef4a5751ab9c0c3b401)
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
# install x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
# https://github.com/Xilinx/linux-xlnx/commit/782658c51bbcd85a39a5d9a51b57224f185d7670
git remote add xlnx https://github.com/Xilinx/linux-xlnx
git fetch --no-tags xlnx xlnx_rebase_v5.4
git checkout 782658c51bbcd85a39a5d9a51b57224f185d7670
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> ld.lld: error: duplicate symbol: dwc3_simple_check_quirks
>>> defined at core.h:1434 (drivers/usb/dwc3/core.h:1434)
>>> usb/dwc3/core.o:(dwc3_simple_check_quirks) in archive drivers/built-in.a
>>> defined at core.h:1434 (drivers/usb/dwc3/core.h:1434)
>>> usb/dwc3/trace.o:(.text+0x40) in archive drivers/built-in.a
--
>> ld.lld: error: duplicate symbol: dwc3_simple_check_quirks
>>> defined at core.h:1434 (drivers/usb/dwc3/core.h:1434)
>>> usb/dwc3/core.o:(dwc3_simple_check_quirks) in archive drivers/built-in.a
>>> defined at core.h:1434 (drivers/usb/dwc3/core.h:1434)
>>> usb/dwc3/host.o:(.text+0x40) in archive drivers/built-in.a
--
>> ld.lld: error: duplicate symbol: dwc3_simple_check_quirks
>>> defined at core.h:1434 (drivers/usb/dwc3/core.h:1434)
>>> usb/dwc3/core.o:(dwc3_simple_check_quirks) in archive drivers/built-in.a
>>> defined at core.h:1434 (drivers/usb/dwc3/core.h:1434)
>>> usb/dwc3/debugfs.o:(.text+0x40) in archive drivers/built-in.a
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 34683 bytes --]
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2021-06-16 7:15 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=202106161520.HWJ1QlIQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=anurag.kumar.vulisha@xilinx.com \
--cc=clang-built-linux@googlegroups.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=monstr@monstr.eu \
--cc=piyush.mehta@xilinx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).