From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Hans de Goede <hdegoede@redhat.com>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: linux-next: Tree for Oct 8 (media/usb/gspca)
Date: Wed, 08 Oct 2014 10:13:39 -0700 [thread overview]
Message-ID: <543570C3.9080207@infradead.org> (raw)
In-Reply-To: <20141008174923.76786a03@canb.auug.org.au>
On 10/07/14 23:49, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any material intended for v3.19 to you linux-next
> included trees until after v3.18-rc1 has been released.
>
> Changes since 20141007:
>
I saw these build errors in gspca when CONFIG_INPUT=m but the gspca
sub-drivers are builtin:
drivers/built-in.o: In function `gspca_dev_probe2':
(.text+0x10ef43): undefined reference to `input_allocate_device'
drivers/built-in.o: In function `gspca_dev_probe2':
(.text+0x10efdd): undefined reference to `input_register_device'
drivers/built-in.o: In function `gspca_dev_probe2':
(.text+0x10f002): undefined reference to `input_free_device'
drivers/built-in.o: In function `gspca_dev_probe2':
(.text+0x10f0ac): undefined reference to `input_unregister_device'
drivers/built-in.o: In function `gspca_disconnect':
(.text+0x10f186): undefined reference to `input_unregister_device'
drivers/built-in.o: In function `sd_int_pkt_scan':
se401.c:(.text+0x11373d): undefined reference to `input_event'
se401.c:(.text+0x11374e): undefined reference to `input_event'
drivers/built-in.o: In function `sd_pkt_scan':
t613.c:(.text+0x119f0e): undefined reference to `input_event'
t613.c:(.text+0x119f1f): undefined reference to `input_event'
drivers/built-in.o: In function `sd_stopN':
t613.c:(.text+0x11a047): undefined reference to `input_event'
drivers/built-in.o:t613.c:(.text+0x11a058): more undefined references to `input_event' follow
These could be fixed in Kconfig by something like (for each sub-driver that tests
CONFIG_INPUT):
depends on INPUT || INPUT=n
Do you have another preference for fixing this?
thanks,
--
~Randy
next prev parent reply other threads:[~2014-10-08 17:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 6:49 linux-next: Tree for Oct 8 Stephen Rothwell
2014-10-08 17:13 ` Randy Dunlap [this message]
2014-10-08 18:31 ` linux-next: Tree for Oct 8 (media/usb/gspca) Mauro Carvalho Chehab
2014-10-08 20:53 ` Randy Dunlap
2014-10-09 1:50 ` Mauro Carvalho Chehab
2014-10-09 6:45 ` Paul Bolle
2014-10-09 10:30 ` Mauro Carvalho Chehab
2014-10-09 11:26 ` Paul Bolle
2014-10-09 11:52 ` Mauro Carvalho Chehab
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=543570C3.9080207@infradead.org \
--to=rdunlap@infradead.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@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.