All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
	Georgi Vlaev <joe@nucleusys.com>,
	Brian Austin <brian.austin@cirrus.com>,
	moderated for non-subscribers <alsa-devel@alsa-project.org>
Subject: Re: linux-next: Tree for Mar 26 (sound/soc/codecs/cs42l52.c)
Date: Wed, 26 Mar 2014 13:01:27 -0700	[thread overview]
Message-ID: <53333217.7090706@infradead.org> (raw)
In-Reply-To: <5332FE45.5030601@infradead.org>

On 03/26/2014 09:20 AM, Randy Dunlap wrote:
> On 03/25/2014 11:35 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>> This tree still fails (more than usual) the powerpc allyesconfig build.
>>
>> Changes since 20140325:
>>
> 
> on x86_64:
> 
> when CONFIG_INPUT=m and
> SNC_SOC_CS42L42=y:

              L52

> 
> sound/built-in.o: In function `cs42l52_beep_set':
> cs42l52.c:(.text+0xd4b01): undefined reference to `input_event'
> sound/built-in.o: In function `cs42l52_probe':
> cs42l52.c:(.text+0xd4beb): undefined reference to `devm_input_allocate_device'
> cs42l52.c:(.text+0xd4d0c): undefined reference to `input_register_device'
> sound/built-in.o: In function `wm8962_beep_set':
> wm8962.c:(.text+0x116240): undefined reference to `input_event'
> sound/built-in.o: In function `wm8962_probe':
> wm8962.c:(.text+0x116cae): undefined reference to `devm_input_allocate_device'
> wm8962.c:(.text+0x116e0e): undefined reference to `input_register_device'
> 
> 
> Full randconfig file is attached.
> 

I think that this can be fixed by modifying the Kconfig file with:

	depends on INPUT || INPUT=n

This will restrict CS42L52 to =m if INPUT=m.

-- 
~Randy

      reply	other threads:[~2014-03-26 20:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26  6:35 linux-next: Tree for Mar 26 Stephen Rothwell
2014-03-26  6:35 ` Stephen Rothwell
2014-03-26 16:20 ` linux-next: Tree for Mar 26 (sound/soc/codecs/cs42l52.c) Randy Dunlap
2014-03-26 20:01   ` Randy Dunlap [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=53333217.7090706@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=brian.austin@cirrus.com \
    --cc=joe@nucleusys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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.