public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "sudhir kumar" <imsudhirkumar@gmail.com>
Cc: linux-kernel@vger.kernel.org, sam@ravnborg.org,
	Hendrik Sattler <post@hendrik-sattler.de>,
	Richard Purdie <rpurdie@rpsys.net>
Subject: Re: [2.6.24-rc6-mm1] Build Failure on ppc64 with CONFIG_USB_GADGET not set.
Date: Mon, 7 Jan 2008 09:49:55 -0800	[thread overview]
Message-ID: <20080107094955.720c3764.akpm@linux-foundation.org> (raw)
In-Reply-To: <3da2c0120801070323v39e6f95esd47cef6b860fbf06@mail.gmail.com>

On Mon, 7 Jan 2008 16:53:58 +0530 "sudhir kumar" <imsudhirkumar@gmail.com> wrote:

> Hi Andrew!
> 
> Kernel build fails on my ppc64 machine. It seems to be  a dependency
> problem with CONFIG_USB_GADGET not set.
> Config file is attached.
> 
>  CC      init/version.o
>   LD      init/built-in.o
>   LD      .tmp_vmlinux1
> drivers/built-in.o: In function `oz99x_remove':
> drivers/i2c/chips/oz99x.c:660: undefined reference to `.led_classdev_unregister'
> drivers/built-in.o: In function `oz99x_configure_leds':
> drivers/i2c/chips/oz99x.c:314: undefined reference to `.led_classdev_register'
> make: *** [.tmp_vmlinux1] Error 1
> 

Strange.

oz99x-i2c-button-and-led-support-driver.patch has

+config OZ99X
+	tristate "O2 Micro/ETC OZ990/OZ992 SMBus chip"
+	depends on I2C
+	select INPUT_POLLDEV
+	select LEDS_CLASS

and your .config gives

box:/usr/src/25> grep LEDS .config
# CONFIG_NEW_LEDS is not set
CONFIG_LEDS_CLASS=y

so drivers/leds/led-class.o should be linked into your vmlinux.  But that
obviously isn't happening.


  reply	other threads:[~2008-01-07 17:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07 11:23 [2.6.24-rc6-mm1] Build Failure on ppc64 with CONFIG_USB_GADGET not set sudhir kumar
2008-01-07 17:49 ` Andrew Morton [this message]
2008-01-07 19:15   ` Sam Ravnborg
2008-01-07 19:36     ` Andrew Morton
2008-01-07 20:07       ` Hendrik Sattler

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=20080107094955.720c3764.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=imsudhirkumar@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=post@hendrik-sattler.de \
    --cc=rpurdie@rpsys.net \
    --cc=sam@ravnborg.org \
    /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