From: Greg KH <gregkh@suse.de>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUILD-FAILURE] next-20090114 - drivers/staging/meilhaus
Date: Wed, 14 Jan 2009 10:04:03 -0800 [thread overview]
Message-ID: <20090114180403.GA16974@suse.de> (raw)
In-Reply-To: <20090114180024.GB4796@linux.vnet.ibm.com>
On Wed, Jan 14, 2009 at 11:30:24PM +0530, Kamalesh Babulal wrote:
> Hi Stephen,
>
> next-20090114 randconfig build on x86_64 machine fails,
>
> LD drivers/staging/meilhaus/built-in.o
> drivers/staging/meilhaus/me1600.o: In function `cleanup_module':
> (.exit.text+0x0): multiple definition of `cleanup_module'
> drivers/staging/meilhaus/memain.o:memain.c:(.exit.text+0x0): first defined here
Yeah, a lot of these staging drivers can't handle being built into the
kernel.
At first glance, I don't see a way to prevent this, is there some
Kconfig option I can use to say, "this can only be a module or disabled,
not build statically"?
thanks,
greg k-h
next prev parent reply other threads:[~2009-01-14 18:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 5:50 linux-next: Tree for January 14 Stephen Rothwell
2009-01-14 17:23 ` linux-next: Tree for January 14 (multimedia/firesat-rc) Randy Dunlap
2009-01-14 22:01 ` Stefan Richter
2009-01-14 22:01 ` Stefan Richter
2009-01-14 22:01 ` Stefan Richter
2009-01-14 17:48 ` [BUILD-FAILURE] next-20090114 - powerpc - drivers/leds/leds-gpio.c Kamalesh Babulal
2009-01-14 17:48 ` Kamalesh Babulal
2009-01-14 17:48 ` Kamalesh Babulal
2009-01-14 18:00 ` [BUILD-FAILURE] next-20090114 - drivers/staging/meilhaus Kamalesh Babulal
2009-01-14 18:04 ` Greg KH [this message]
2009-01-14 18:11 ` Randy Dunlap
2009-01-14 18:50 ` Greg KH
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=20090114180403.GA16974@suse.de \
--to=gregkh@suse.de \
--cc=kamalesh@linux.vnet.ibm.com \
--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;
as well as URLs for NNTP newsgroup(s).