linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	moderated for non-subscribers <alsa-devel@alsa-project.org>,
	Cezary Rojewski <cezary.rojewski@intel.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	Jie Yang <yang.jie@linux.intel.com>
Subject: Re: linux-next: Tree for Dec 17 (sound/soc/intel/boards/cml_rt1011_rt5682.o)
Date: Tue, 17 Dec 2019 08:04:25 -0800	[thread overview]
Message-ID: <c4fd86fb-586a-0fbc-74b0-97e6b99ef2ca@infradead.org> (raw)
In-Reply-To: <20191217130829.6a66b404@canb.auug.org.au>

On 12/16/19 6:08 PM, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20191216:
> 

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",
    ^~~~~~~~
../sound/soc/intel/boards/cml_rt1011_rt5682.c:407:50: warning: missing braces around initializer [-Wmissing-braces]
 static struct snd_soc_codec_conf rt1011_conf[] = {
                                                  ^
../sound/soc/intel/boards/cml_rt1011_rt5682.c:409:15:
   .dev_name = "i2c-10EC1011:00",
               {                }
../sound/soc/intel/boards/cml_rt1011_rt5682.c:413:4: error: ‘struct snd_soc_codec_conf’ has no member named ‘dev_name’
   .dev_name = "i2c-10EC1011:01",
    ^~~~~~~~
../sound/soc/intel/boards/cml_rt1011_rt5682.c:407:50: warning: missing braces around initializer [-Wmissing-braces]
 static struct snd_soc_codec_conf rt1011_conf[] = {
                                                  ^
../sound/soc/intel/boards/cml_rt1011_rt5682.c:409:15:
   .dev_name = "i2c-10EC1011:00",
               {                }
../sound/soc/intel/boards/cml_rt1011_rt5682.c:413:15:
   .dev_name = "i2c-10EC1011:01",
               {                }
../sound/soc/intel/boards/cml_rt1011_rt5682.c:417:4: error: ‘struct snd_soc_codec_conf’ has no member named ‘dev_name’
   .dev_name = "i2c-10EC1011:02",
    ^~~~~~~~
../sound/soc/intel/boards/cml_rt1011_rt5682.c:407:50: warning: missing braces around initializer [-Wmissing-braces]
 static struct snd_soc_codec_conf rt1011_conf[] = {
                                                  ^
../sound/soc/intel/boards/cml_rt1011_rt5682.c:409:15:
   .dev_name = "i2c-10EC1011:00",
               {                }
../sound/soc/intel/boards/cml_rt1011_rt5682.c:413:15:
   .dev_name = "i2c-10EC1011:01",
               {                }
../sound/soc/intel/boards/cml_rt1011_rt5682.c:417:15:
   .dev_name = "i2c-10EC1011:02",
               {                }
../sound/soc/intel/boards/cml_rt1011_rt5682.c:421:4: error: ‘struct snd_soc_codec_conf’ has no member named ‘dev_name’
   .dev_name = "i2c-10EC1011:03",
    ^~~~~~~~
../sound/soc/intel/boards/cml_rt1011_rt5682.c:407:50: warning: missing braces around initializer [-Wmissing-braces]
 static struct snd_soc_codec_conf rt1011_conf[] = {
                                                  ^
../sound/soc/intel/boards/cml_rt1011_rt5682.c:409:15:
   .dev_name = "i2c-10EC1011:00",
               {                }
../sound/soc/intel/boards/cml_rt1011_rt5682.c:413:15:
   .dev_name = "i2c-10EC1011:01",
               {                }
../sound/soc/intel/boards/cml_rt1011_rt5682.c:417:15:
   .dev_name = "i2c-10EC1011:02",
               {                }
../sound/soc/intel/boards/cml_rt1011_rt5682.c:421:15:
   .dev_name = "i2c-10EC1011:03",
               {                }
../sound/soc/intel/boards/cml_rt1011_rt5682.c:407:50: warning: missing braces around initializer [-Wmissing-braces]
 static struct snd_soc_codec_conf rt1011_conf[] = {
                                                  ^
../sound/soc/intel/boards/cml_rt1011_rt5682.c:409:15:
   .dev_name = "i2c-10EC1011:00",
               {                }
../sound/soc/intel/boards/cml_rt1011_rt5682.c:413:15:
   .dev_name = "i2c-10EC1011:01",
               {                }
../sound/soc/intel/boards/cml_rt1011_rt5682.c:417:15:
   .dev_name = "i2c-10EC1011:02",
               {                }
../sound/soc/intel/boards/cml_rt1011_rt5682.c:421:15:
   .dev_name = "i2c-10EC1011:03",
               {                }
make[5]: *** [../scripts/Makefile.build:266: sound/soc/intel/boards/cml_rt1011_rt5682.o] Error 1


-- 
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>

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

Thread overview: 3+ 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 ` Randy Dunlap [this message]
2019-12-17 16:41   ` [alsa-devel] linux-next: Tree for Dec 17 (sound/soc/intel/boards/cml_rt1011_rt5682.o) 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=c4fd86fb-586a-0fbc-74b0-97e6b99ef2ca@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=alsa-devel@alsa-project.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=pierre-louis.bossart@linux.intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).