From: Vinod Koul <vinod.koul@intel.com>
To: Liam Girdwood <liam.r.girdwood@linux.intel.com>
Cc: kbuild test robot <fengguang.wu@intel.com>,
alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
kbuild-all@01.org
Subject: Re: [asoc:topic/topology 104/105] :undefined reference to `snd_soc_dapm_new_control'
Date: Mon, 15 Jun 2015 11:12:05 +0530 [thread overview]
Message-ID: <20150615054205.GR28601@localhost> (raw)
In-Reply-To: <1433427189.19747.53.camel@loki>
On Thu, Jun 04, 2015 at 03:13:09PM +0100, Liam Girdwood wrote:
> On Thu, 2015-06-04 at 13:04 +0100, Mark Brown wrote:
> > On Thu, Jun 04, 2015 at 06:58:38PM +0800, kbuild test robot wrote:
> >
> > > All error/warnings (new ones prefixed by >>):
> > >
> > > sound/built-in.o: In function `soc_tplg_dapm_widget_create':
> > > >> :(.text+0x25a90): undefined reference to `snd_soc_dapm_new_control'
> >
> > The fix for the build bug in your patch exporting this was to add a
> > static prototype (you were in the CC for that fix) so now the topology
> > code still doesn't have the export.
> >
> > Can you send a fixup please?
>
> Sorry, appended below. I can resend separately if required.
I dont think Mark applied this, can you please resend
--
~Vinod
>
>
> From 3df449a45fcde9f63dd34683d4216a73bd900f98 Mon Sep 17 00:00:00 2001
> From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
> Date: Thu, 4 Jun 2015 15:08:34 +0100
> Subject: [PATCH] ASoC: DAPM: fix build errors for missing
> snd_soc_dapm_new_control symbol
>
> Fix the following error:-
>
> All error/warnings (new ones prefixed by >>):
> >
> > sound/built-in.o: In function `soc_tplg_dapm_widget_create':
> > >> :(.text+0x25a90): undefined reference to `snd_soc_dapm_new_control'
>
> Signed-off-by: Liam Girdwood <liam.r.girdwood@linux.intel.com>
> ---
> sound/soc/soc-dapm.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/sound/soc/soc-dapm.c b/sound/soc/soc-dapm.c
> index 92d57a9..1b4a6eb 100644
> --- a/sound/soc/soc-dapm.c
> +++ b/sound/soc/soc-dapm.c
> @@ -53,7 +53,7 @@ static int snd_soc_dapm_add_path(struct snd_soc_dapm_context *dapm,
> int (*connected)(struct snd_soc_dapm_widget *source,
> struct snd_soc_dapm_widget *sink));
>
> -static struct snd_soc_dapm_widget *
> +struct snd_soc_dapm_widget *
> snd_soc_dapm_new_control(struct snd_soc_dapm_context *dapm,
> const struct snd_soc_dapm_widget *widget);
>
> @@ -3270,7 +3270,7 @@ int snd_soc_dapm_put_pin_switch(struct snd_kcontrol *kcontrol,
> }
> EXPORT_SYMBOL_GPL(snd_soc_dapm_put_pin_switch);
>
> -static struct snd_soc_dapm_widget *
> +struct snd_soc_dapm_widget *
> snd_soc_dapm_new_control(struct snd_soc_dapm_context *dapm,
> const struct snd_soc_dapm_widget *widget)
> {
> --
> 2.1.4
>
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
--
next prev parent reply other threads:[~2015-06-15 5:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 10:58 [asoc:topic/topology 104/105] :undefined reference to `snd_soc_dapm_new_control' kbuild test robot
2015-06-04 12:04 ` Mark Brown
2015-06-04 14:13 ` Liam Girdwood
2015-06-15 5:42 ` Vinod Koul [this message]
2015-06-15 16:46 ` Liam Girdwood
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=20150615054205.GR28601@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=liam.r.girdwood@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