public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
	driverdevel <devel@driverdev•osuosl.org>, gregkh <greg@kroah•com>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
	Andres Salomon <dilinger@queued•net>, Chris Ball <cjb@laptop•org>,
	Jon Nettleton <jon.nettleton@gmail•com>
Subject: [PATCH] staging: fix olpc_dcon build, needs BACKLIGHT_CLASS_DEVICE
Date: Wed, 25 May 2011 19:17:06 -0700	[thread overview]
Message-ID: <20110525191706.a6b0f357.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20110525135844.2a25f858.sfr@canb.auug.org.au>

From: Randy Dunlap <randy.dunlap@oracle•com>

Fix olpc_dcon.c build by selecting the needed kconfig symbol
BACKLIGHT_CLASS_DEVICE.

olpc_dcon.c:(.text+0x11588b): undefined reference to `backlight_device_register'

Signed-off-by: Randy Dunlap <randy.dunlap@oracle•com>
Cc: Andres Salomon <dilinger@queued•net>
Cc: Chris Ball <cjb@laptop•org>
Cc: Jon Nettleton <jon.nettleton@gmail•com>
---
 drivers/staging/olpc_dcon/Kconfig |    1 +
 1 file changed, 1 insertion(+)

--- linux-next-20110525.orig/drivers/staging/olpc_dcon/Kconfig
+++ linux-next-20110525/drivers/staging/olpc_dcon/Kconfig
@@ -2,6 +2,7 @@ config FB_OLPC_DCON
 	tristate "One Laptop Per Child Display CONtroller support"
 	depends on OLPC && FB
 	select I2C
+	select BACKLIGHT_CLASS_DEVICE
 	---help---
 	  Add support for the OLPC XO DCON controller.  This controller is
 	  only available on OLPC platforms.   Unless you have one of these

      reply	other threads:[~2011-05-26  2:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25  3:58 linux-next: Tree for May 25 Stephen Rothwell
2011-05-26  2:17 ` 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=20110525191706.a6b0f357.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle$(echo .)com \
    --cc=cjb@laptop$(echo .)org \
    --cc=devel@driverdev$(echo .)osuosl.org \
    --cc=dilinger@queued$(echo .)net \
    --cc=greg@kroah$(echo .)com \
    --cc=jon.nettleton@gmail$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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