public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	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: Re: linux-next: build failure after merge of the sound-asoc-fixes tree
Date: Tue, 28 Oct 2025 09:34:11 +1100	[thread overview]
Message-ID: <20251028093411.605431d0@canb.auug.org.au> (raw)
In-Reply-To: <20251024120920.23f707f5@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 1487 bytes --]

Hi all,

On Fri, 24 Oct 2025 12:09:20 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Fri, 24 Oct 2025 00:49:11 +0100 Mark Brown <broonie@kernel.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.

I am still getting this failure.  I cannot find anything that would
have interacted with this addition of name_prefix.  I can only
speculate that maybe this file was not built in the past for an x86_64
allmodconfig (i.e. some KCONFIG change) or an update to an include file
has messed being committed.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2025-10-27 22:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-23 23:19 linux-next: build failure after merge of the sound-asoc-fixes tree Stephen Rothwell
2025-10-23 23:49 ` Mark Brown
2025-10-24  1:09   ` Stephen Rothwell
2025-10-27 22:34     ` Stephen Rothwell [this message]
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=20251028093411.605431d0@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rf@opensource.cirrus.com \
    --cc=shumingf@realtek.com \
    --cc=yung-chuan.liao@linux.intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox