From: kbuild test robot <lkp@intel.com>
To: Cyrille Pitchen <cyrille.pitchen@atmel.com>
Cc: kbuild-all@01.org, lars@metafoo.de, lgirdwood@gmail.com,
broonie@kernel.org, perex@perex.cz, tiwai@suse.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Cyrille Pitchen <cyrille.pitchen@atmel.com>
Subject: Re: [PATCH v2 1/1] ASoC: ad193x: add support to ad1934
Date: Tue, 29 Sep 2015 21:57:38 +0800 [thread overview]
Message-ID: <201509292117.icTMOV93%fengguang.wu@intel.com> (raw)
In-Reply-To: <fd52e5f435e77591a47ac4980a400888cea8c3bb.1443527716.git.cyrille.pitchen@atmel.com>
[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]
Hi Cyrille,
[auto build test results on v4.3-rc3 -- if it's inappropriate base, please ignore]
config: x86_64-allmodconfig (attached as .config)
reproduce:
git checkout b88bda3bf6b85650c3a00c734d5e27905daa7c27
# save the attached .config to linux build tree
make ARCH=x86_64
All error/warnings (new ones prefixed by >>):
sound/soc/codecs/ad193x.c: In function 'ad193x_codec_probe':
>> sound/soc/codecs/ad193x.c:392:41: error: 'struct snd_soc_codec' has no member named 'dapm'
ret = snd_soc_dapm_new_controls(&codec->dapm,
^
sound/soc/codecs/ad193x.c:400:39: error: 'struct snd_soc_codec' has no member named 'dapm'
ret = snd_soc_dapm_add_routes(&codec->dapm,
^
vim +392 sound/soc/codecs/ad193x.c
386 num);
387 if (ret)
388 return ret;
389
390 /* add adc widgets */
391 num = ARRAY_SIZE(ad193x_adc_widgets);
> 392 ret = snd_soc_dapm_new_controls(&codec->dapm,
393 ad193x_adc_widgets,
394 num);
395 if (ret)
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 50052 bytes --]
prev parent reply other threads:[~2015-09-29 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 11:59 Cyrille Pitchen
2015-09-29 13:57 ` kbuild test robot [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=201509292117.icTMOV93%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cyrille.pitchen@atmel.com \
--cc=kbuild-all@01.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®