From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mark Brown <broonie@kernel•org>
Cc: Bard Liao <yung-chuan.liao@linux•intel.com>,
Jack Yu <jack.yu@realtek•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux•intel.com>
Subject: linux-next: build failure after merge of the regmap tree
Date: Fri, 27 Nov 2020 18:24:11 +1100 [thread overview]
Message-ID: <20201127182411.07c15471@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
Hi all,
After merging the regmap tree, today's linux-next build (powerpc
allyesconfig) failed like this:
ld: sound/soc/codecs/rt715-sdca.o:(.opd+0xf0): multiple definition of `rt715_init'; sound/soc/codecs/rt715.o:(.opd+0x108): first defined here
ld: sound/soc/codecs/rt715-sdca.o: in function `.rt715_init':
rt715-sdca.c:(.text.rt715_init+0x0): multiple definition of `.rt715_init'; sound/soc/codecs/rt715.o:rt715.c:(.text.rt715_init+0x0): first defined here
ld: sound/soc/codecs/rt715-sdca.o:(.opd+0x108): multiple definition of `rt715_io_init'; sound/soc/codecs/rt715.o:(.opd+0x120): first defined here
ld: sound/soc/codecs/rt715-sdca.o: in function `.rt715_io_init':
rt715-sdca.c:(.text.rt715_io_init+0x0): multiple definition of `.rt715_io_init'; sound/soc/codecs/rt715.o:rt715.c:(.text.rt715_io_init+0x0): first defined here
Caused by commit
6f4a038b9967 ("ASoC/SoundWire: rt715-sdca: First version of rt715 sdw sdca codec driver")
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-11-27 7:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 7:24 Stephen Rothwell [this message]
2020-11-30 17:59 ` linux-next: build failure after merge of the regmap tree Mark Brown
2020-11-30 18:07 ` Pierre-Louis Bossart
2020-11-30 18:11 ` Mark Brown
2020-11-30 18:21 ` Pierre-Louis Bossart
-- strict thread matches above, loose matches on Subject: below --
2017-11-02 0:57 Stephen Rothwell
2012-04-11 4:13 Stephen Rothwell
2012-04-11 8:17 ` Mark Brown
2012-02-27 4:05 Stephen Rothwell
[not found] <C3AE124F08223B42BC95AEB82F0F6CED1F9D0895@KCHJEXMB01.kpit.com>
2011-12-15 9:25 ` Ashish Jangam
2011-12-15 18:25 ` Grant Likely
2011-12-16 7:19 ` Ashish Jangam
2011-12-16 8:11 ` Grant Likely
2011-12-16 8:15 ` Ashish Jangam
2011-12-16 8:25 ` Grant Likely
2011-12-15 6:17 Stephen Rothwell
2011-12-15 6:05 Stephen Rothwell
2011-12-15 6:17 ` Mark Brown
2011-12-15 6:24 ` Ashish Jangam
2011-09-29 5:18 Stephen Rothwell
2011-09-29 9:43 ` Mark Brown
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=20201127182411.07c15471@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=broonie@kernel$(echo .)org \
--cc=jack.yu@realtek$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=pierre-louis.bossart@linux$(echo .)intel.com \
--cc=yung-chuan.liao@linux$(echo .)intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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