All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manjunatha Halli <x0130808@ti.com>
To: Randy Dunlap <rdunlap@xenotime.net>
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>
Subject: Re: linux-next: Tree for Feb 2 (media/radio/wl128x)
Date: Thu, 2 Feb 2012 11:20:56 -0600	[thread overview]
Message-ID: <4F2AC5F8.1000901@ti.com> (raw)
In-Reply-To: <4F2AD0E4.6020801@xenotime.net>

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.

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.
>
>

WARNING: multiple messages have this Message-ID (diff)
From: Manjunatha Halli <x0130808@ti.com>
To: Randy Dunlap <rdunlap@xenotime.net>
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>
Subject: Re: linux-next: Tree for Feb 2 (media/radio/wl128x)
Date: Thu, 2 Feb 2012 11:20:56 -0600	[thread overview]
Message-ID: <4F2AC5F8.1000901@ti.com> (raw)
In-Reply-To: <4F2AD0E4.6020801@xenotime.net>

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.

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.
>
>


  reply	other threads:[~2012-02-02 17:20 UTC|newest]

Thread overview: 24+ 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 [this message]
2012-02-02 17:20     ` Manjunatha Halli
2012-02-02 18:40     ` [PATCH] " Randy Dunlap
2012-02-02 18:20       ` Manjunatha Halli
2012-02-02 18:20         ` 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: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 18:24   ` Randy Dunlap
2012-02-02 23:44   ` Stephen Rothwell
2012-02-02 23:44     ` Stephen Rothwell
2012-02-03  0:41     ` Brian Norris
2012-02-03  0:41       ` Brian Norris
2012-02-03  5:37   ` Artem Bityutskiy
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=4F2AC5F8.1000901@ti.com \
    --to=x0130808@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=manjunatha_halli@ti.com \
    --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 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.