From mboxrd@z Thu Jan 1 00:00:00 1970 From: Randy Dunlap Subject: Re: linux-next: Tree for January 12 (cifs vs. staging) Date: Mon, 12 Jan 2009 10:19:10 -0800 Message-ID: <496B899E.7060605@oracle.com> References: <20090112154539.4857f533.sfr@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from rcsinet11.oracle.com ([148.87.113.123]:58677 "EHLO rgminet11.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752680AbZALST7 (ORCPT ); Mon, 12 Jan 2009 13:19:59 -0500 In-Reply-To: <20090112154539.4857f533.sfr@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: linux-next@vger.kernel.org, LKML , sfrench@samba.org, Greg KH Stephen Rothwell wrote: > Hi all, > > Some people took me at my word and so we have the 2.6.30 code starting to > trickle in already. When CIFS is built-in (=y) and staging/rt28[67]0 =y, there are multiple definitions of: build-r8250.out:(.text+0x1d8ad0): multiple definition of `MD5Init' build-r8250.out:(.text+0x1dbb30): multiple definition of `MD5Update' build-r8250.out:(.text+0x1db9b0): multiple definition of `MD5Final' all of which need to have more unique identifiers for their global symbols (e.g., rt28_md5_init, cifs_md5_init, foo, blah, bar). -- ~Randy