From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mark Brown <broonie@kernel•org>, Liam Girdwood <lgirdwood@gmail•com>
Cc: Bard Liao <yung-chuan.liao@linux•intel.com>,
Shuming Fan <shumingf@realtek•com>,
Richard Fitzgerald <rf@opensource•cirrus.com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure after merge of the sound-asoc-fixes tree
Date: Fri, 24 Oct 2025 10:19:31 +1100 [thread overview]
Message-ID: <20251024101931.49f46027@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2047 bytes --]
Hi all,
After merging the sound-asoc-fixes tree, today's linux-next build
(x86_64 allmodconfig) failed like this:
sound/soc/sdw_utils/soc_sdw_utils.c:316:18: error: 'struct asoc_sdw_codec_info' has no member named 'name_prefix'
316 | .name_prefix = "rt1320",
| ^~~~~~~~~~~
sound/soc/sdw_utils/soc_sdw_utils.c:316:32: error: initialization of 'int' from 'char *' makes integer from pointer without a cast [-Wint-conversion]
316 | .name_prefix = "rt1320",
| ^~~~~~~~
sound/soc/sdw_utils/soc_sdw_utils.c:316:32: note: (near initialization for 'codec_info_list[12].version_id')
sound/soc/sdw_utils/soc_sdw_utils.c:316:32: error: initializer element is not computable at load time
sound/soc/sdw_utils/soc_sdw_utils.c:316:32: note: (near initialization for 'codec_info_list[12].version_id')
sound/soc/sdw_utils/soc_sdw_utils.c:564:18: error: 'struct asoc_sdw_codec_info' has no member named 'name_prefix'
564 | .name_prefix = "AMP",
| ^~~~~~~~~~~
sound/soc/sdw_utils/soc_sdw_utils.c:564:32: error: initialization of 'int' from 'char *' makes integer from pointer without a cast [-Wint-conversion]
564 | .name_prefix = "AMP",
| ^~~~~
sound/soc/sdw_utils/soc_sdw_utils.c:564:32: note: (near initialization for 'codec_info_list[23].version_id')
sound/soc/sdw_utils/soc_sdw_utils.c:564:32: error: initializer element is not computable at load time
sound/soc/sdw_utils/soc_sdw_utils.c:564:32: note: (near initialization for 'codec_info_list[23].version_id')
Caused by commits
3293d3d7b088 ("ASoC: sdw_utils: add name_prefix for rt1321 part id")
61eb4112a8fb ("ASoC: soc_sdw_utils: add cs35l57 support")
But something else has changed because 3293d3d7b088 was also in
yesterday's linux-next - which did not fail to build.
I have used the sound-asoc-fixes tree from next-20251022 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-10-23 23:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 23:19 Stephen Rothwell [this message]
2025-10-23 23:49 ` linux-next: build failure after merge of the sound-asoc-fixes tree Mark Brown
2025-10-24 1:09 ` Stephen Rothwell
2025-10-27 22:34 ` Stephen Rothwell
2025-10-27 22:37 ` Stephen Rothwell
2025-10-28 11:53 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2025-02-07 4:28 Stephen Rothwell
2019-11-12 21:10 Stephen Rothwell
2019-11-14 22:34 ` Stephen Rothwell
2019-11-18 15:58 ` Mark Brown
2019-11-18 16:47 ` Pierre-Louis Bossart
2019-11-18 19:14 ` Mark Brown
2019-11-19 3:15 ` 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=20251024101931.49f46027@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=broonie@kernel$(echo .)org \
--cc=lgirdwood@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rf@opensource$(echo .)cirrus.com \
--cc=shumingf@realtek$(echo .)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