From: Randy Dunlap <rdunlap@infradead.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: linux-media@vger.kernel.org,
Mauro Carvalho Chehab <m.chehab@samsung.com>,
kbuild-all@01.org
Subject: Re: [linuxtv-media:devel 498/499] av7110.c:undefined reference to `av7110_ir_exit'
Date: Fri, 15 Aug 2014 17:07:59 -0700 [thread overview]
Message-ID: <53EEA0DF.6090903@infradead.org> (raw)
In-Reply-To: <53ee83cb.H8pPJAwEaBRBZftj%fengguang.wu@intel.com>
On 08/15/14 15:03, kbuild test robot wrote:
> tree: git://linuxtv.org/media_tree.git devel
> head: f1d2fd677f61bf4d649098317497db11a958a021
> commit: 277c0ffaea64c71c39f03b9ee6818de600c38fc3 [498/499] [media] media: ttpci: build av7110_ir.c only when allowed by CONFIG_INPUT_EVDEV
> config: x86_64-randconfig-s1-08160530 (attached as .config)
Argh, thanks, fix is on the way.
> All error/warnings:
>
> drivers/built-in.o: In function `av7110_detach':
>>> av7110.c:(.text+0x228d4a): undefined reference to `av7110_ir_exit'
> drivers/built-in.o: In function `arm_thread':
>>> av7110.c:(.text+0x22a404): undefined reference to `av7110_check_ir_config'
>>> av7110.c:(.text+0x22a626): undefined reference to `av7110_check_ir_config'
> drivers/built-in.o: In function `av7110_attach':
>>> av7110.c:(.text+0x22b08c): undefined reference to `av7110_ir_init'
>
> ---
> 0-DAY kernel build testing backend Open Source Technology Center
> http://lists.01.org/mailman/listinfo/kbuild Intel Corporation
>
--
~Randy
prev parent reply other threads:[~2014-08-16 0:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 22:03 [linuxtv-media:devel 498/499] av7110.c:undefined reference to `av7110_ir_exit' kbuild test robot
2014-08-16 0:07 ` 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=53EEA0DF.6090903@infradead.org \
--to=rdunlap@infradead.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.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;
as well as URLs for NNTP newsgroup(s).