From: Pierre-Louis Bossart <pierre-louis.bossart@linux•intel.com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Mark Brown <broonie@kernel•org>,
Liam Girdwood <lgirdwood@gmail•com>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Hui Wang <hui.wang@canonical•com>,
Rander Wang <rander.wang@linux•intel.com>,
Vinod Koul <vkoul@kernel•org>,
Bard liao <yung-chuan.liao@linux•intel.com>
Subject: Re: linux-next: build failures after merge of the sound-asoc tree
Date: Tue, 14 Apr 2020 22:28:10 -0500 [thread overview]
Message-ID: <f73485eb-c0c8-c557-7491-5daabce4d3de@linux.intel.com> (raw)
In-Reply-To: <20200415121521.3e40b591@canb.auug.org.au>
On 4/14/20 9:15 PM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the sound-asoc tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> sound/soc/intel/boards/skl_hda_dsp_generic.c: In function 'skl_set_hda_codec_autosuspend_delay':
> sound/soc/intel/boards/skl_hda_dsp_generic.c:178:37: error: 'struct snd_soc_pcm_runtime' has no member named 'codec_dai'
> 178 | struct snd_soc_dai *codec_dai = rtd->codec_dai;
Yes, I just sent a fix for this.
> | ^~
> drivers/soundwire/intel.c: In function 'sdw_stream_setup':
> drivers/soundwire/intel.c:672:39: error: 'struct snd_soc_pcm_runtime' has no member named 'codec_dais'
> 672 | ret = snd_soc_dai_set_sdw_stream(rtd->codec_dais[i], sdw_stream,
> | ^~
> In file included from include/linux/device.h:15,
> from include/linux/acpi.h:15,
> from drivers/soundwire/intel.c:8:
> drivers/soundwire/intel.c:676:8: error: 'struct snd_soc_pcm_runtime' has no member named 'codec_dais'
> 676 | rtd->codec_dais[i]->name);
Bard, can you take care of the SoundWire change - this needs to change
to asoc_rtd_to_codec(rtd, i)
Thanks!
next prev parent reply other threads:[~2020-04-15 3:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 2:15 linux-next: build failures after merge of the sound-asoc tree Stephen Rothwell
2020-04-15 3:28 ` Pierre-Louis Bossart [this message]
2020-04-16 17:22 ` 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=f73485eb-c0c8-c557-7491-5daabce4d3de@linux.intel.com \
--to=pierre-louis.bossart@linux$(echo .)intel.com \
--cc=broonie@kernel$(echo .)org \
--cc=hui.wang@canonical$(echo .)com \
--cc=lgirdwood@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rander.wang@linux$(echo .)intel.com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=vkoul@kernel$(echo .)org \
--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