public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel•org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux•intel.com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
	Liam Girdwood <lgirdwood@gmail•com>,
	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: Thu, 16 Apr 2020 18:22:19 +0100	[thread overview]
Message-ID: <20200416172219.GO5354@sirena.org.uk> (raw)
In-Reply-To: <f73485eb-c0c8-c557-7491-5daabce4d3de@linux.intel.com>

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

On Tue, Apr 14, 2020 at 10:28:10PM -0500, Pierre-Louis Bossart wrote:
> On 4/14/20 9:15 PM, Stephen Rothwell wrote:

> > 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)

Bard?

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

      reply	other threads:[~2020-04-16 17:22 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
2020-04-16 17:22   ` Mark Brown [this message]

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=20200416172219.GO5354@sirena.org.uk \
    --to=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=pierre-louis.bossart@linux$(echo .)intel.com \
    --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