From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
driverdevel <devel@driverdev.osuosl.org>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Andres Salomon <dilinger@queued.net>
Subject: Re: linux-next: Tree for April 11 (staging/olpc_dcon)
Date: Mon, 11 Apr 2011 08:52:00 -0700 [thread overview]
Message-ID: <20110411085200.b2f22e34.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20110411135049.148ef002.sfr@canb.auug.org.au>
On Mon, 11 Apr 2011 13:50:49 +1000 Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20110408:
olpc_dcon.c:(.text+0x11588b): undefined reference to `backlight_device_register'
Hmph. I thought that adding
depends on BACKLIGHT_CLASS_DEVICE
would be sufficient, but noooooo, that spews:
drivers/i2c/Kconfig:5:error: recursive dependency detected!
drivers/i2c/Kconfig:5: symbol I2C is selected by FB_OLPC_DCON
drivers/staging/olpc_dcon/Kconfig:1: symbol FB_OLPC_DCON depends on BACKLIGHT_CLASS_DEVICE
drivers/video/backlight/Kconfig:125: symbol BACKLIGHT_CLASS_DEVICE is selected by PANEL_SHARP_LS037V7DW01
drivers/video/omap2/displays/Kconfig:18: symbol PANEL_SHARP_LS037V7DW01 depends on OMAP2_DSS
drivers/video/omap2/dss/Kconfig:1: symbol OMAP2_DSS is selected by VIDEO_OMAP2_VOUT
drivers/media/video/omap/Kconfig:1: symbol VIDEO_OMAP2_VOUT depends on VIDEO_CAPTURE_DRIVERS
drivers/media/video/Kconfig:73: symbol VIDEO_CAPTURE_DRIVERS depends on VIDEO_V4L2
drivers/media/video/Kconfig:5: symbol VIDEO_V4L2 depends on VIDEO_V4L2_COMMON
drivers/media/Kconfig:51: symbol VIDEO_V4L2_COMMON depends on I2C
Any other suggestions?
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2011-04-11 15:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 3:50 linux-next: Tree for April 11 Stephen Rothwell
2011-04-11 15:52 ` 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=20110411085200.b2f22e34.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=dilinger@queued.net \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox