From: Randy Dunlap <rdunlap@xenotime.net>
To: Manjunatha Halli <x0130808@ti.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Manjunatha Halli <manjunatha_halli@ti.com>,
Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: [PATCH] Re: linux-next: Tree for Feb 2 (media/radio/wl128x)
Date: Thu, 02 Feb 2012 10:40:30 -0800 [thread overview]
Message-ID: <4F2AD89E.70805@xenotime.net> (raw)
In-Reply-To: <4F2AC5F8.1000901@ti.com>
On 02/02/2012 09:20 AM, Manjunatha Halli wrote:
> Hi Randy Dunlap,
>
> In config file you are missing the CONFIG_TI_ST config which builds the TI's shared transport driver upon which the FM driver works.
>
> Please select this config in drivers/misc/ti-st/Kconfig which will solve the problem.
Wrong answer.
The problem seems to be that GPIOLIB is not enabled, but wl128x Kconfig says:
config RADIO_WL128X
tristate "Texas Instruments WL128x FM Radio"
depends on VIDEO_V4L2 && RFKILL
select TI_ST if NET && GPIOLIB
so TI_ST is not selected here.
The Kconfig files should handle this properly.
Here is one possible fix for you to consider.
---
From: Randy Dunlap <rdunlap@xenotime.net>
Fix build errors when GPIOLIB is not enabled.
Fix wl128x Kconfig to depend on GPIOLIB since TI_ST also
depends on GPIOLIB.
(.text+0xe6d60): undefined reference to `st_register'
(.text+0xe7016): undefined reference to `st_unregister'
(.text+0xe70ce): undefined reference to `st_unregister'
Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
Cc: Manjunatha Halli <manjunatha_halli@ti.com>
---
drivers/media/radio/wl128x/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- linux-next-20120202.orig/drivers/media/radio/wl128x/Kconfig
+++ linux-next-20120202/drivers/media/radio/wl128x/Kconfig
@@ -4,8 +4,8 @@
menu "Texas Instruments WL128x FM driver (ST based)"
config RADIO_WL128X
tristate "Texas Instruments WL128x FM Radio"
- depends on VIDEO_V4L2 && RFKILL
- select TI_ST if NET && GPIOLIB
+ depends on VIDEO_V4L2 && RFKILL && GPIOLIB
+ select TI_ST if NET
help
Choose Y here if you have this FM radio chip.
> Regards
> Manju
>
> On 02/02/2012 12:07 PM, Randy Dunlap wrote:
>> On 02/01/2012 07:45 PM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20120201:
>>
>> drivers/built-in.o: In function `fmc_prepare':
>> (.text+0xe6d60): undefined reference to `st_register'
>> drivers/built-in.o: In function `fmc_prepare':
>> (.text+0xe7016): undefined reference to `st_unregister'
>> drivers/built-in.o: In function `fmc_release':
>> (.text+0xe70ce): undefined reference to `st_unregister'
>>
>>
>> Full randconfig file is attached.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2012-02-02 17:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 3:45 linux-next: Tree for Feb 2 Stephen Rothwell
2012-02-02 18:07 ` linux-next: Tree for Feb 2 (media/radio/wl128x) Randy Dunlap
2012-02-02 17:20 ` Manjunatha Halli
2012-02-02 18:40 ` Randy Dunlap [this message]
2012-02-02 18:20 ` [PATCH] " Manjunatha Halli
2012-02-05 20:32 ` Randy Dunlap
2012-02-02 18:10 ` linux-next: Tree for Feb 2 (trace/events/sunrpc.h) Randy Dunlap
2012-02-09 2:37 ` Steven Rostedt
2012-02-09 3:14 ` Myklebust, Trond
2012-02-09 3:30 ` Steven Rostedt
2012-02-09 16:14 ` Randy Dunlap
2012-02-02 18:24 ` linux-next: Tree for Feb 2 (fs/jffs2) Randy Dunlap
2012-02-02 23:44 ` Stephen Rothwell
2012-02-03 0:41 ` Brian Norris
2012-02-03 5:37 ` Artem Bityutskiy
2012-02-02 23:28 ` linux-next: Tree for Feb 2 (kvmtool) Randy Dunlap
2012-03-27 10:19 ` Pekka Enberg
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=4F2AD89E.70805@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=manjunatha_halli@ti.com \
--cc=mchehab@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=x0130808@ti.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).