From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mark Brown <broonie@kernel•org>, Liam Girdwood <lgirdwood@gmail•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux•intel.com>,
Irina Tirdea <irina.tirdea@intel•com>
Subject: linux-next: build warnings after merge of the sound-asoc tree
Date: Tue, 16 Aug 2016 11:36:01 +1000 [thread overview]
Message-ID: <20160816113601.574c1fcf@canb.auug.org.au> (raw)
Hi all,
After merging the sound-asoc tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
WARNING: sound/soc/intel/boards/snd-soc-sst-bytcr-rt5640.o(.text+0x7e7): Section mismatch in reference from the function snd_byt_rt5640_mc_probe() to the variable .init.rodata:cpu_ids.43814
The function snd_byt_rt5640_mc_probe() references
the variable __initconst cpu_ids.43814.
This is often because snd_byt_rt5640_mc_probe lacks a __initconst
annotation or the annotation of cpu_ids.43814 is wrong.
WARNING: sound/soc/intel/boards/snd-soc-sst-bytcr-rt5640.o(.text+0x9d5): Section mismatch in reference from the function snd_byt_rt5640_mc_probe() to the variable .init.rodata:cpu_ids.43814
The function snd_byt_rt5640_mc_probe() references
the variable __initconst cpu_ids.43814.
This is often because snd_byt_rt5640_mc_probe lacks a __initconst
annotation or the annotation of cpu_ids.43814 is wrong.
WARNING: sound/soc/intel/atom/sst/snd-intel-sst-acpi.o(.text+0x20f): Section mismatch in reference from the function sst_acpi_probe() to the variable .init.rodata:cpu_ids.44453
The function sst_acpi_probe() references
the variable __initconst cpu_ids.44453.
This is often because sst_acpi_probe lacks a __initconst
annotation or the annotation of cpu_ids.44453 is wrong.
WARNING: sound/soc/intel/atom/sst/snd-intel-sst-acpi.o(.text+0x20f): Section mismatch in reference from the function sst_acpi_probe() to the variable .init.rodata:cpu_ids.44453
The function sst_acpi_probe() references
the variable __initconst cpu_ids.44453.
This is often because sst_acpi_probe lacks a __initconst
annotation or the annotation of cpu_ids.44453 is wrong.
WARNING: sound/soc/intel/boards/snd-soc-sst-bytcr-rt5640.o(.text+0x7e7): Section mismatch in reference from the function snd_byt_rt5640_mc_probe() to the variable .init.rodata:cpu_ids.43814
The function snd_byt_rt5640_mc_probe() references
the variable __initconst cpu_ids.43814.
This is often because snd_byt_rt5640_mc_probe lacks a __initconst
annotation or the annotation of cpu_ids.43814 is wrong.
WARNING: sound/soc/intel/boards/snd-soc-sst-bytcr-rt5640.o(.text+0x9d5): Section mismatch in reference from the function snd_byt_rt5640_mc_probe() to the variable .init.rodata:cpu_ids.43814
The function snd_byt_rt5640_mc_probe() references
the variable __initconst cpu_ids.43814.
This is often because snd_byt_rt5640_mc_probe lacks a __initconst
annotation or the annotation of cpu_ids.43814 is wrong.
I am not sure which commit(s) introduced these.
--
Cheers,
Stephen Rothwell
next reply other threads:[~2016-08-16 1:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 1:36 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-31 1:43 linux-next: build warnings after merge of the sound-asoc tree Stephen Rothwell
2016-05-31 8:16 ` Charles Keepax
2012-04-20 4:28 Stephen Rothwell
2012-04-23 9:35 ` Liam Girdwood
2011-04-12 2:05 Stephen Rothwell
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=20160816113601.574c1fcf@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=broonie@kernel$(echo .)org \
--cc=irina.tirdea@intel$(echo .)com \
--cc=lgirdwood@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=pierre-louis.bossart@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