public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	gregkh@suse.de, sjakub@gmail.com
Subject: Re: linux-next-20081120 - staging - asus_oled device build fails with !CONFIG_USB_SUPPORT
Date: Thu, 20 Nov 2008 22:39:27 +0530	[thread overview]
Message-ID: <20081120170927.GB4821@linux.vnet.ibm.com> (raw)
In-Reply-To: <20081120212907.efc2276b.sfr@canb.auug.org.au>

Hi Stephen,

	next-2001120 kernel randconfig build fails with build failure
drivers/built-in.o: In function `enable_oled':
asus_oled.c:(.text+0x170d26): undefined reference to `usb_bulk_msg'
drivers/built-in.o: In function `send_packet':
asus_oled.c:(.text+0x170e5e): undefined reference to `usb_bulk_msg'
drivers/built-in.o: In function `send_packets':
asus_oled.c:(.text+0x170fd4): undefined reference to `usb_bulk_msg'
drivers/built-in.o: In function `asus_oled_disconnect':
asus_oled.c:(.text+0x171761): undefined reference to `usb_put_dev'
drivers/built-in.o: In function `asus_oled_probe':
asus_oled.c:(.text+0x17189f): undefined reference to `usb_get_dev'
asus_oled.c:(.text+0x171a4c): undefined reference to `usb_put_dev'
drivers/built-in.o: In function `asus_oled_init':
asus_oled.c:(.init.text+0xdabe): undefined reference to `usb_register_driver'
drivers/built-in.o: In function `asus_oled_exit':
asus_oled.c:(.exit.text+0x2281): undefined reference to `usb_deregister'

asus_oled depends on the CONFIG_USB_SUPPORT, I have only build tested
the patch.

Signed-off-by: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
---
--- linux/drivers/staging/asus_oled/Kconfig	2008-11-20 11:50:43.000000000 -0500
+++ linux/drivers/staging/asus_oled/~Kconfig	2008-11-20 11:50:35.000000000 -0500
@@ -1,5 +1,6 @@
 config ASUS_OLED
 	tristate "Asus OLED driver"
+	depends on USB_SUPPORT
 	default N
 	---help---
 	  Enable support for the OLED display present in some Asus laptops.
-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.

  parent reply	other threads:[~2008-11-20 17:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-20 10:29 linux-next: Tree for November 20 Stephen Rothwell
2008-11-20 16:16 ` linux-next-20081120 - staging - meilhaus driver build fails Kamalesh Babulal
2008-11-21 19:02   ` Greg KH
2008-11-20 17:09 ` Kamalesh Babulal [this message]
2008-11-21 19:02   ` linux-next-20081120 - staging - asus_oled device build fails with !CONFIG_USB_SUPPORT Greg KH
2008-11-20 20:52 ` linux-next: Tree for November 20 (staging* [lots]) 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=20081120170927.GB4821@linux.vnet.ibm.com \
    --to=kamalesh@linux.vnet.ibm.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=sjakub@gmail.com \
    /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