All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Cezary Rojewski <cezary.rojewski@intel.com>,
	Jie Yang <yang.jie@linux.intel.com>,
	moderated for non-subscribers <alsa-devel@alsa-project.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	Mark Brown <broonie@kernel.org>
Subject: Re: [alsa-devel] linux-next: Tree for Dec 17 (sound/soc/intel/boards/cml_rt1011_rt5682.o)
Date: Tue, 17 Dec 2019 10:41:45 -0600	[thread overview]
Message-ID: <94745c3a-33aa-b307-06d6-ba0c8dddc9d2@linux.intel.com> (raw)
In-Reply-To: <c4fd86fb-586a-0fbc-74b0-97e6b99ef2ca@infradead.org>




> on x86_64:
> 
>    CC      sound/soc/intel/boards/cml_rt1011_rt5682.o
> ../sound/soc/intel/boards/cml_rt1011_rt5682.c:409:4: error: ‘struct snd_soc_codec_conf’ has no member named ‘dev_name’
>     .dev_name = "i2c-10EC1011:00",

ACK, thanks for reporting this conflict with ee8f537fd8b71c ('ASoC: 
soc-core: remove legacy style of codec_conf')

Will send a patch in the next 30mn.



WARNING: multiple messages have this Message-ID (diff)
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Cezary Rojewski <cezary.rojewski@intel.com>,
	Jie Yang <yang.jie@linux.intel.com>,
	moderated for non-subscribers <alsa-devel@alsa-project.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	Mark Brown <broonie@kernel.org>
Subject: Re: [alsa-devel] linux-next: Tree for Dec 17 (sound/soc/intel/boards/cml_rt1011_rt5682.o)
Date: Tue, 17 Dec 2019 10:41:45 -0600	[thread overview]
Message-ID: <94745c3a-33aa-b307-06d6-ba0c8dddc9d2@linux.intel.com> (raw)
In-Reply-To: <c4fd86fb-586a-0fbc-74b0-97e6b99ef2ca@infradead.org>




> on x86_64:
> 
>    CC      sound/soc/intel/boards/cml_rt1011_rt5682.o
> ../sound/soc/intel/boards/cml_rt1011_rt5682.c:409:4: error: ‘struct snd_soc_codec_conf’ has no member named ‘dev_name’
>     .dev_name = "i2c-10EC1011:00",

ACK, thanks for reporting this conflict with ee8f537fd8b71c ('ASoC: 
soc-core: remove legacy style of codec_conf')

Will send a patch in the next 30mn.


_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2019-12-17 16:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-17  2:08 linux-next: Tree for Dec 17 Stephen Rothwell
2019-12-17 16:04 ` linux-next: Tree for Dec 17 (sound/soc/intel/boards/cml_rt1011_rt5682.o) Randy Dunlap
2019-12-17 16:04   ` [alsa-devel] " Randy Dunlap
2019-12-17 16:41   ` Pierre-Louis Bossart [this message]
2019-12-17 16:41     ` Pierre-Louis Bossart

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=94745c3a-33aa-b307-06d6-ba0c8dddc9d2@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=yang.jie@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.