linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andres Salomon <dilinger@queued.net>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, gregkh <greg@kroah.com>,
	driverdevel <devel@driverdev.osuosl.org>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Chris Ball <cjb@laptop.org>,
	Jon Nettleton <jon.nettleton@gmail.com>
Subject: Re: [PATCH -next] staging: fix olpc_dcon kconfig and build errors
Date: Mon, 21 Feb 2011 21:29:33 -0800	[thread overview]
Message-ID: <20110221212933.573a8a3e@debxo> (raw)
In-Reply-To: <20110221143908.96e03b3c.randy.dunlap@oracle.com>

Looks correct, thanks!

Acked-By: Andres Salomon <dilinger@queued.net>


On Mon, 21 Feb 2011
14:39:08 -0800 Randy Dunlap <randy.dunlap@oracle.com> wrote:

> From: Randy Dunlap <randy.dunlap@oracle.com>
> 
> drivers/staging/olpc_dcon/olpc_dcon_xo_1_5.c:106: error:
> 'acpi_gbl_FADT' undeclared (first use in this function)
> 
> Fixing that one gives:
> 
> ERROR:
> "backlight_device_register" [drivers/staging/olpc_dcon/olpc-dcon.ko]
> undefined! ERROR:
> "registered_fb" [drivers/staging/olpc_dcon/olpc-dcon.ko] undefined!
> ERROR: "lock_fb_info" [drivers/staging/olpc_dcon/olpc-dcon.ko]
> undefined! ERROR:
> "backlight_device_unregister" [drivers/staging/olpc_dcon/olpc-dcon.ko]
> undefined! ERROR:
> "num_registered_fb" [drivers/staging/olpc_dcon/olpc-dcon.ko]
> undefined! ERROR: "fb_blank" [drivers/staging/olpc_dcon/olpc-dcon.ko]
> undefined!
> 
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> Cc: Greg Kroah-Hartman <greg@kroah.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 |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> --- linux-next-20110221.orig/drivers/staging/olpc_dcon/Kconfig
> +++ linux-next-20110221/drivers/staging/olpc_dcon/Kconfig
> @@ -1,6 +1,6 @@
>  config FB_OLPC_DCON
>  	tristate "One Laptop Per Child Display CONtroller support"
> -	depends on OLPC
> +	depends on OLPC && FB
>  	select I2C
>  	---help---
>  	  Add support for the OLPC XO DCON controller.  This
> controller is @@ -19,7 +19,7 @@ config FB_OLPC_DCON_1
>  
>  config FB_OLPC_DCON_1_5
>  	bool "OLPC XO-1.5 DCON support"
> -	depends on FB_OLPC_DCON
> +	depends on FB_OLPC_DCON && ACPI
>  	default y
>  	---help---
>  	  Enable support for the DCON in XO-1.5 model laptops.  The
> kernel

      reply	other threads:[~2011-02-22  5:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-21  7:21 linux-next: Tree for February 21 Stephen Rothwell
2011-02-21 17:57 ` linux-next: Tree for February 21 (usb/serial) Randy Dunlap
2011-02-21 20:30   ` Rafael J. Wysocki
     [not found]     ` <201102212130.01789.rjw-KKrjLPT3xs0@public.gmane.org>
2011-03-03 21:51       ` Randy Dunlap
2011-03-04 15:04         ` Alan Stern
2011-03-15 15:36           ` Randy Dunlap
2011-02-21 22:39 ` [PATCH -next] staging: fix olpc_dcon kconfig and build errors Randy Dunlap
2011-02-22  5:29   ` Andres Salomon [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=20110221212933.573a8a3e@debxo \
    --to=dilinger@queued.net \
    --cc=cjb@laptop.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=greg@kroah.com \
    --cc=jon.nettleton@gmail.com \
    --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 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).