linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Hans Verkuil <hans.verkuil@cisco.com>,
	Randy Dunlap <rdunlap@xenotime.net>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	linux-media <linux-media@vger.kernel.org>
Subject: Re: radio-maxiradio.c: undefined reference to `snd_tea575x_init'
Date: Thu, 7 Jun 2012 06:27:32 +0900	[thread overview]
Message-ID: <20120606212732.GA8093@localhost> (raw)
In-Reply-To: <201206062315.04124.hverkuil@xs4all.nl>

On Wed, Jun 06, 2012 at 11:15:04PM +0200, Hans Verkuil wrote:
> On Wed June 6 2012 22:40:14 Fengguang Wu wrote:
> > On Thu, Mar 29, 2012 at 09:38:38AM -0700, Randy Dunlap wrote:
> > > On 03/28/2012 08:42 PM, Stephen Rothwell wrote:
> > > 
> > > > Hi all,
> > > > 
> > > > Reminder: please do not add stuff destined for v3.5 to linux-next
> > > > included trees/branches until after v3.4-rc1 has been released.
> > > > 
> > > > Changes since 20120328:
> > > 
> > > 
> > > on x86_64:
> > > 
> > > radio-maxiradio.c:(.devinit.text+0x356ac): undefined reference to `snd_tea575x_init'
> > > radio-maxiradio.c:(.devexit.text+0x503e): undefined reference to `snd_tea575x_exit'
> > 
> > I run into this issue, too, in the 3.5-rc1 based tip/master.
> > 
> >         drivers/built-in.o: In function `maxiradio_probe':
> >          radio-maxiradio.c:(.devinit.text+0x35a27): undefined reference to `snd_tea575x_init'
> >         drivers/built-in.o: In function `maxiradio_remove':
> >          radio-maxiradio.c:(.devexit.text+0x6754): undefined reference to `snd_tea575x_exit'
> > 
> > Any fixes available now? The related commit is:
> > 
> >         commit cfb19b0ab13847a0e0e49521eb94113b0b315e3b
> >         Author: Hans Verkuil <hans.verkuil@cisco.com>
> >         Date:   Sun Feb 5 09:53:17 2012 -0300
> > 
> >             [media] radio-maxiradio: use the tea575x framework
> >             
> >             This card is based on the tea575x receiver. Use the tea575x-tuner framework
> >             instead of reinventing the wheel.
> >             
> >             Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
> >             Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
> > 
> > Thanks,
> > Fengguang
> 
> Works for me with 3.5-rc1. There was a fix done in sound/pci/Kconfig that
> should have solved this.

Nice.

> Is CONFIG_SND_TEA575X defined? Do you have a snd_tea575x_tuner module?

Sorry I lost the .config. I'll report back if the error shows up again.

Thanks,
Fengguang

      reply	other threads:[~2012-06-06 21:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-29  3:42 linux-next: Tree for Mar 29 Stephen Rothwell
2012-03-29 16:18 ` [PATCH -next] hid: fix WACOM Kconfig warning Randy Dunlap
2012-03-29 16:21   ` Przemo Firszt
2012-03-29 16:38 ` linux-next: Tree for Mar 29 (radio + snd) Randy Dunlap
2012-06-06 20:40   ` radio-maxiradio.c: undefined reference to `snd_tea575x_init' Fengguang Wu
2012-06-06 21:15     ` Hans Verkuil
2012-06-06 21:27       ` Fengguang Wu [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=20120606212732.GA8093@localhost \
    --to=fengguang.wu@intel.com \
    --cc=hans.verkuil@cisco.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=sfr@canb.auug.org.au \
    /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).