linux-kernel - Re: linux-next: Tree for March 24 (staging/vt66*)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4BAB8362.7030005@oracle.com>
Date:	Thu, 25 Mar 2010 08:38:10 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Forest Bond <forest@...ttletooquiet.net>
CC:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	devel@...verdev.osuosl.org, Greg KH <gregkh@...e.de>
Subject: Re: linux-next: Tree for March 24 (staging/vt66*)

On 03/25/10 06:00, Forest Bond wrote:
> Hi,
> 
> On Wed, Mar 24, 2010 at 12:44:08PM -0700, Randy Dunlap wrote:
>> On 03/23/10 22:17, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20100323:
>>
>>
>>
>> (.text+0x5d140): multiple definition of `hostap_set_hostapd'
>> (.text+0x5ccab): multiple definition of `hostap_ioctl'
>>
>> when
>> CONFIG_HOSTAP=y
>> and
>> CONFIG_VT665[56]=y
>>
>> or just both of the latter are =y.
> 
> Is there any way to limit CONFIG_VT665[56] to ("n", "m")?  That would be
> sufficient as a work-around, right?

A driver can be limited to [nm] by adding:
	depends on m

> Or is it preferable to rename the offending functions?

Yes, it's preferable to rename them.

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