From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>
Subject: Re: linux-next: Tree for November 20 (snd_jack)
Date: Fri, 20 Nov 2009 10:40:30 -0800 [thread overview]
Message-ID: <20091120104030.01972d33.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20091120230513.0d2e5cb5.sfr@canb.auug.org.au>
On Fri, 20 Nov 2009 23:05:13 +1100 Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20091119:
This commit in linux-next-20091120:
author Mark Brown <broonie@opensource.wolfsonmicro.com>
Mon, 28 Jul 2008 18:05:36 +0000 (19:05 +0100)
committer Jaroslav Kysela <perex@perex.cz>
Tue, 29 Jul 2008 19:32:06 +0000 (21:32 +0200)
commit 0d94e41abe271c86df06bcf72d24f9ca7ce771f0
causes build errors when:
CONFIG_INPUT=m
CONFIG_SND=y
CONFIG_SND_JACK=y
CONFIG_SND_SOC=m
CONFIG_SND_HDA_INTEL=m
CONFIG_SND_HDA_INPUT_JACK=y
At least part of the problem is that when a tristate kconfig symbol with
a value of 'm' selects a boolean kconfig symbol, the boolean becomes 'y',
so we end up with
snd-$(CONFIG_SND_JACK) += jack.o
being built into the kernel image and INPUT=m, giving:
sound/built-in.o: In function `snd_jack_report':
(.text+0xb5c5): undefined reference to `input_event'
sound/built-in.o: In function `snd_jack_report':
(.text+0xb627): undefined reference to `input_event'
sound/built-in.o: In function `snd_jack_dev_register':
jack.c:(.text+0xb736): undefined reference to `input_register_device'
sound/built-in.o: In function `snd_jack_dev_free':
jack.c:(.text+0xb806): undefined reference to `input_unregister_device'
jack.c:(.text+0xb861): undefined reference to `input_free_device'
sound/built-in.o: In function `snd_jack_new':
(.text+0xb953): undefined reference to `input_allocate_device'
sound/built-in.o: In function `snd_jack_new':
(.text+0xba0d): undefined reference to `input_set_capability'
sound/built-in.o: In function `snd_jack_new':
(.text+0xba2c): undefined reference to `input_free_device'
---
~Randy
next prev parent reply other threads:[~2009-11-20 18:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 12:05 linux-next: Tree for November 20 Stephen Rothwell
2009-11-20 18:40 ` Randy Dunlap [this message]
2009-11-20 19:15 ` linux-next: Tree for November 20 (snd_jack) Takashi Iwai
2009-11-20 19:21 ` Takashi Iwai
2009-11-20 19:34 ` Randy Dunlap
2009-11-21 19:02 ` Takashi Iwai
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=20091120104030.01972d33.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=perex@perex.cz \
--cc=sfr@canb.auug.org.au \
--cc=tiwai@suse.de \
/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