From: Mark Brown <broonie@kernel.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: alsa-devel@alsa-project.org, kbuild-all@01.org,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Subject: Re: [asoc:topic/wm9705 1/1] sound/soc/codecs/wm9705.c:330:18: error: implicit declaration of function 'snd_soc_new_ac97_component'; did you mean 'snd_soc_new_ac97_codec'?
Date: Mon, 12 Feb 2018 14:49:11 +0000 [thread overview]
Message-ID: <20180212144911.GD12976@sirena.org.uk> (raw)
In-Reply-To: <201802122255.cGsOCM1z%fengguang.wu@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 612 bytes --]
On Mon, Feb 12, 2018 at 10:19:57PM +0800, kbuild test robot wrote:
> sound/soc/codecs/wm9705.c: In function 'wm9705_soc_probe':
> >> sound/soc/codecs/wm9705.c:330:18: error: implicit declaration of function 'snd_soc_new_ac97_component'; did you mean 'snd_soc_new_ac97_codec'? [-Werror=implicit-function-declaration]
> wm9705->ac97 = snd_soc_new_ac97_component(component, WM9705_VENDOR_ID,
> ^~~~~~~~~~~~~~~~~~~~~~~~~~
> snd_soc_new_ac97_codec
I've dropped this and the other patch that had the same issue. I wonder
why 0day didn't notice this on the list...
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2018-02-12 14:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 14:19 [asoc:topic/wm9705 1/1] sound/soc/codecs/wm9705.c:330:18: error: implicit declaration of function 'snd_soc_new_ac97_component'; did you mean 'snd_soc_new_ac97_codec'? kbuild test robot
2018-02-12 14:49 ` Mark Brown [this message]
2018-02-13 0:36 ` Kuninori Morimoto
2018-02-13 12:05 ` Mark Brown
2018-02-13 2:48 ` Fengguang Wu
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=20180212144911.GD12976@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=kuninori.morimoto.gx@renesas.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).