public inbox for linux-kernel@vger.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>,
	linux-media <linux-media@vger.kernel.org>,
	Holger Waechtler <holger@convergence.de>,
	Oliver Endriss <o.endriss@gmx.de>
Subject: Re: linux-next: Tree for Jul 11 (media/pci/ttpci/av7110)
Date: Fri, 11 Jul 2014 11:31:19 -0700	[thread overview]
Message-ID: <53C02D77.4070809@infradead.org> (raw)
In-Reply-To: <20140711171844.39fcbb50@canb.auug.org.au>

On 07/11/14 00:18, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20140710:
> 

on x86_64:

CONFIG_DVB_AV7110=y
CONFIG_INPUT_EVDEV=m

drivers/built-in.o: In function `av7110_emit_keyup':
av7110_ir.c:(.text+0x76b608): undefined reference to `input_event'
av7110_ir.c:(.text+0x76b61a): undefined reference to `input_event'
drivers/built-in.o: In function `av7110_emit_key':
av7110_ir.c:(.text+0x76b6b4): undefined reference to `input_event'
av7110_ir.c:(.text+0x76b6cd): undefined reference to `input_event'
av7110_ir.c:(.text+0x76b7b0): undefined reference to `input_event'
drivers/built-in.o:av7110_ir.c:(.text+0x76b7ca): more undefined references to `input_event' follow
drivers/built-in.o: In function `av7110_ir_init':
(.text+0x76bcdb): undefined reference to `input_allocate_device'
drivers/built-in.o: In function `av7110_ir_init':
(.text+0x76bf93): undefined reference to `input_register_device'
drivers/built-in.o: In function `av7110_ir_init':
(.text+0x76c073): undefined reference to `input_free_device'
drivers/built-in.o: In function `av7110_ir_exit':
(.text+0x76c1db): undefined reference to `input_unregister_device'


-- 
~Randy

  reply	other threads:[~2014-07-11 18:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-11  7:18 linux-next: Tree for Jul 11 Stephen Rothwell
2014-07-11 18:31 ` Randy Dunlap [this message]
2014-07-12 22:26 ` Nick Krause
2014-07-13  4:08   ` Nick Krause

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=53C02D77.4070809@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=holger@convergence.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=o.endriss@gmx.de \
    --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