linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Tinghan Shen <tinghan.shen@mediatek.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Mark Brown <broonie@kernel.org>,
	Allen-KH Cheng <allen-kh.cheng@mediatek.com>,
	Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
	Yaochun Hung <yc.hung@mediatek.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: [linux-next:master 6086/6873] ld.lld: error: duplicate symbol: sof_hifixdsp_boot_sequence
Date: Wed, 27 Apr 2022 13:47:53 +0800	[thread overview]
Message-ID: <202204271301.UWzhiTRP-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   088fb7eff3496e0f61fdf68bda89b81a4d0a4434
commit: 570c14dc92d5dc6f732cb74fa691ef909d182710 [6086/6873] ASoC: SOF: mediatek: Add mt8186 sof fw loader and dsp ops
config: hexagon-allyesconfig (https://download.01.org/0day-ci/archive/20220427/202204271301.UWzhiTRP-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 1cddcfdc3c683b393df1a5c9063252eb60e52818)
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://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=570c14dc92d5dc6f732cb74fa691ef909d182710
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout 570c14dc92d5dc6f732cb74fa691ef909d182710
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=hexagon SHELL=/bin/bash

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

Note: the linux-next/master HEAD 088fb7eff3496e0f61fdf68bda89b81a4d0a4434 builds fine.
      It may have been fixed somewhere.

All errors (new ones prefixed by >>):

>> ld.lld: error: duplicate symbol: sof_hifixdsp_boot_sequence
   >>> defined at mt8195-loader.c
   >>> soc/sof/mediatek/mt8195/mt8195-loader.o:(sof_hifixdsp_boot_sequence) in archive sound/built-in.a
   >>> defined at mt8186-loader.c
   >>> soc/sof/mediatek/mt8186/mt8186-loader.o:(.text+0x0) in archive sound/built-in.a
--
>> ld.lld: error: duplicate symbol: sof_hifixdsp_shutdown
   >>> defined at mt8195-loader.c
   >>> soc/sof/mediatek/mt8195/mt8195-loader.o:(sof_hifixdsp_shutdown) in archive sound/built-in.a
   >>> defined at mt8186-loader.c
   >>> soc/sof/mediatek/mt8186/mt8186-loader.o:(.text+0x150) in archive sound/built-in.a

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp


                 reply	other threads:[~2022-04-27  5:48 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=202204271301.UWzhiTRP-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=allen-kh.cheng@mediatek.com \
    --cc=broonie@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=llvm@lists.linux.dev \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=tinghan.shen@mediatek.com \
    --cc=yc.hung@mediatek.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).