From: Greg KH <greg@kroah.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
gregkh@suse.de, devel@driverdev.osuosl.org,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] staging: cx25821 and go7007 depend on IR_CORE
Date: Thu, 16 Sep 2010 12:33:33 -0700 [thread overview]
Message-ID: <20100916193333.GE10397@kroah.com> (raw)
In-Reply-To: <20100914152359.f871d000.randy.dunlap@oracle.com>
On Tue, Sep 14, 2010 at 03:23:59PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Fix build errors in cx25821 and go7007.
> They both use IR functions, so they should depend on IR_CORE.
> (It's not safe to select VIDEO_IR when IR_CORE is not enabled.)
>
> (.text+0x39065a): undefined reference to `ir_core_debug'
> (.text+0x3906a4): undefined reference to `ir_core_debug'
> ir-functions.c:(.text+0x39080b): undefined reference to `ir_core_debug'
> (.text+0x390893): undefined reference to `ir_g_keycode_from_table'
> (.text+0x390942): undefined reference to `ir_core_debug'
> (.text+0x3909f5): undefined reference to `ir_core_debug'
> (.text+0x390a3a): undefined reference to `ir_core_debug'
> (.text+0x390ab1): undefined reference to `ir_core_debug'
> (.text+0x390b36): undefined reference to `ir_core_debug'
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> Cc: devel@driverdev.osuosl.org
> ---
> drivers/staging/cx25821/Kconfig | 2 +-
> drivers/staging/go7007/Kconfig | 2 +-
These need to go to Mauro.
thanks,
greg k-h
next prev parent reply other threads:[~2010-09-16 19:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 3:58 linux-next: Tree for September 14 Stephen Rothwell
2010-09-14 22:23 ` [PATCH -next] mfd: ab8500 depends on SPI_MASTER Randy Dunlap
2010-09-14 22:23 ` [PATCH -next] staging: cx25821 and go7007 depend on IR_CORE Randy Dunlap
2010-09-16 19:33 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-09-17 17:01 Randy Dunlap
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=20100916193333.GE10397@kroah.com \
--to=greg@kroah.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--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.