All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Vinod Koul <vinod.koul@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 17:46:44 +0100	[thread overview]
Message-ID: <1434386804.2434.36.camel@loki> (raw)
In-Reply-To: <20150615054205.GR28601@localhost>

On Mon, 2015-06-15 at 11:12 +0530, Vinod Koul wrote:
> 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
> 

Resending.

Liam

      reply	other threads:[~2015-06-15 16:47 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
2015-06-15 16:46       ` Liam Girdwood [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=1434386804.2434.36.camel@loki \
    --to=liam.r.girdwood@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=vinod.koul@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.