[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251024120920.23f707f5@canb.auug.org.au>
Date: Fri, 24 Oct 2025 12:09:20 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Mark Brown <broonie@...nel.org>
Cc: Liam Girdwood <lgirdwood@...il.com>, Bard Liao
<yung-chuan.liao@...ux.intel.com>, Shuming Fan <shumingf@...ltek.com>,
Richard Fitzgerald <rf@...nsource.cirrus.com>, Linux Kernel Mailing List
<linux-kernel@...r.kernel.org>, Linux Next Mailing List
<linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the sound-asoc-fixes
tree
Hi Mark,
On Fri, 24 Oct 2025 00:49:11 +0100 Mark Brown <broonie@...nel.org> wrote:
>
> On Fri, Oct 24, 2025 at 10:19:31AM +1100, Stephen Rothwell wrote:
> > 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",
> > | ^~~~~~~~
>
> And I do x86 allmodconfig builds which should stop something that breaks
> getting published...
Yeah, so there must be an interaction with something merged before your
tree ... but I couldn't find anything obvious, sorry.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists