From: Sergio Luis <sergio@larces.uece.br>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org, Marek Vasut <marek.vasut@gmail.com>
Subject: Re: [PATCH] drivers/mfd/ucb1400_core.c: fix undefined reference to `ac97_bus_type'
Date: Mon, 13 Oct 2008 00:38:56 -0300 [thread overview]
Message-ID: <48F2C2D0.3000805@larces.uece.br> (raw)
In-Reply-To: <20081012150328.b272975c.randy.dunlap@oracle.com>
Randy Dunlap wrote:
> On Sun, 12 Oct 2008 13:18:13 -0300 Sergio Luis wrote:
>
>> randconfig got a problem with ucb1400_core.c (config attached)
>>
>> drivers/built-in.o:(.data+0x15ab4): undefined reference to `ac97_bus_type'
>> make: *** [.tmp_vmlinux1] Error 1
>>
>> ucb1400 is an ac97 audio codec. express this dependency in Kconfig
>>
>> Signed-off-by: Sergio Luis <sergio@larces.uece.br>
>> Cc: Marek Vasut <marek.vasut@gmail.com>
>>
>> drivers/mfd/Kconfig | 1 +
>> 1 files changed, 1 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
>> index 0dae245..fa851c5 100644
>> --- a/drivers/mfd/Kconfig
>> +++ b/drivers/mfd/Kconfig
>> @@ -52,6 +52,7 @@ config HTC_PASIC3
>>
>> config UCB1400_CORE
>> tristate "Philips UCB1400 Core driver"
>> + select AC97_BUS
>> help
>> This enables support for the Philips UCB1400 core functions.
>> The UCB1400 is an AC97 audio codec.
>
> Hi,
>
> Andrew has a "depends on AC97_BUS" patch queued and approved... fwiw.
>
> The problem with "select AC97_BUS" is that SOUND could be =n and
> selecting AC97_BUS still will not enable SOUND, so it's useless
> (unless/until kconfig is taught to follow select dependencies).
>
> ---
> ~Randy
Ah, yeah, you are correct. Thanks for the explanation.
Sergio.
prev parent reply other threads:[~2008-10-13 3:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-12 16:18 [PATCH] drivers/mfd/ucb1400_core.c: fix undefined reference to `ac97_bus_type' Sergio Luis
2008-10-12 22:03 ` Randy Dunlap
2008-10-13 3:38 ` Sergio Luis [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=48F2C2D0.3000805@larces.uece.br \
--to=sergio@larces.uece.br \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.vasut@gmail.com \
--cc=randy.dunlap@oracle.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