From: kbuild test robot <lkp@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, kbuild-all@01.org
Subject: [sound:for-linus 23/27] (.init.text+0x118): multiple definition of `arch_init_clk_ops'; arch/sh/kernel/cpu/sh2/clock-sh7619.o:(.init.text+0x0): first defined here
Date: Tue, 12 Feb 2019 17:30:41 +0800 [thread overview]
Message-ID: <201902121713.7Ph1n2Ps%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git for-linus
head: 00a399cad1a063e7665f06b6497a807db20441fd
commit: c97617a81a7616d49bc3700959e08c6c6f447093 [23/27] ALSA: hda/ca0132 - Fix build error without CONFIG_PCI
config: sh-allmodconfig (attached as .config)
compiler: sh4-linux-gnu-gcc (Debian 8.2.0-11) 8.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout c97617a81a7616d49bc3700959e08c6c6f447093
# save the attached .config to linux build tree
GCC_VERSION=8.2.0 make.cross ARCH=sh
All errors (new ones prefixed by >>):
sh4-linux-gnu-ld: arch/sh/boards/of-generic.o: in function `plat_irq_setup':
(.init.text+0x134): multiple definition of `plat_irq_setup'; arch/sh/kernel/cpu/sh2/setup-sh7619.o:(.init.text+0x30): first defined here
sh4-linux-gnu-ld: arch/sh/boards/of-generic.o: in function `arch_init_clk_ops':
>> (.init.text+0x118): multiple definition of `arch_init_clk_ops'; arch/sh/kernel/cpu/sh2/clock-sh7619.o:(.init.text+0x0): first defined here
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 50823 bytes --]
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
reply other threads:[~2019-02-12 9:32 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=201902121713.7Ph1n2Ps%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=kbuild-all@01.org \
--cc=tiwai@suse.de \
/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.