Date: Wed, 14 Jan 2009 10:50:29 -0800
From: Greg KH <gregkh@suse.de>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
       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
Message-ID: <20090114185029.GA29674@suse.de>
References: <20090114165002.3bbe49d7.sfr@canb.auug.org.au> <20090114180024.GB4796@linux.vnet.ibm.com> <20090114180403.GA16974@suse.de> <496E2AEE.3060709@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <496E2AEE.3060709@oracle.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1114
Lines: 31

On Wed, Jan 14, 2009 at 10:11:58AM -0800, Randy Dunlap wrote:
> Greg KH wrote:
> > 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"?
> 
> 	depends on m

Doh, it's even documented!

Thanks, I'll go fix that all up.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/