From: Takashi Iwai <tiwai@suse.de>
To: Jim Davis <jim.epost@gmail.com>
Cc: David Henningsson <david.henningsson@canonical.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next <linux-next@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
perex <perex@perex.cz>,
alsa-devel@alsa-project.org
Subject: Re: randconfig build error with next-20150113, in sound/pci/hda/patch_realtek.c
Date: Tue, 13 Jan 2015 20:54:36 +0100 [thread overview]
Message-ID: <s5hvbka1mo3.wl-tiwai@suse.de> (raw)
In-Reply-To: <CA+r1ZhjRNChpFtkTiaE6vfYVxWme2FjjPYwsTR9nodhfZ8KU3w@mail.gmail.com>
At Tue, 13 Jan 2015 11:39:12 -0700,
Jim Davis wrote:
>
> Building with the attached random configuration file,
>
> sound/built-in.o: In function `alc280_fixup_hp_gpio2_mic_hotkey':
> /home/jim/linux/sound/pci/hda/patch_realtek.c:3512: undefined
> reference to `input_allocate_device'
> /home/jim/linux/sound/pci/hda/patch_realtek.c:3520: undefined
> reference to `input_register_device'
> /home/jim/linux/sound/pci/hda/patch_realtek.c:3522: undefined
> reference to `input_free_device'
> /home/jim/linux/sound/pci/hda/patch_realtek.c:3550: undefined
> reference to `input_unregister_device'
> sound/built-in.o: In function `gpio2_mic_hotkey_event':
> /home/jim/linux/include/linux/input.h:392: undefined reference to `input_event'
> /home/jim/linux/include/linux/input.h:417: undefined reference to `input_event'
> /home/jim/linux/include/linux/input.h:392: undefined reference to `input_event'
> /home/jim/linux/include/linux/input.h:417: undefined reference to `input_event'
> make: *** [vmlinux] Error 1
Thanks. So this is the case where the audio driver is built-in while
the input driver is module.
I guess the cleanest workaround is just to select INPUT from
SND_HDA_CODEC_REALTEK in sound/pci/hda/Kconfig. Practically seen,
CONFIG_INPUT is always set, so there must be no real drawback with it.
(And we can reduce a few lines as a bonus.)
David, care to prepare a patch?
thanks,
Takashi
prev parent reply other threads:[~2015-01-13 19:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 18:39 randconfig build error with next-20150113, in sound/pci/hda/patch_realtek.c Jim Davis
2015-01-13 19:54 ` Takashi Iwai [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=s5hvbka1mo3.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
--cc=jim.epost@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=perex@perex.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox