From: Randy Dunlap <randy.dunlap@oracle.com>
To: Forest Bond <forest@alittletooquiet.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
devel@driverdev.osuosl.org, Greg KH <gregkh@suse.de>
Subject: Re: linux-next: Tree for March 24 (staging/vt66*)
Date: Thu, 25 Mar 2010 08:38:10 -0700 [thread overview]
Message-ID: <4BAB8362.7030005@oracle.com> (raw)
In-Reply-To: <20100325130003.GB24056@alittletooquiet.net>
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
next prev parent reply other threads:[~2010-03-25 15:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 5:17 linux-next: Tree for March 24 Stephen Rothwell
2010-03-24 7:29 ` Dmitry Torokhov
2010-03-24 19:44 ` linux-next: Tree for March 24 (staging/vt66*) Randy Dunlap
2010-03-25 13:00 ` Forest Bond
2010-03-25 15:38 ` Randy Dunlap [this message]
2010-04-17 15:03 ` [PATCH] vt6656: Rename hostap_set_hostapd, hostap_iotctl Forest Bond
2010-04-17 15:03 ` [PATCH] vt6655: " Forest Bond
2010-03-24 20:19 ` linux-next: Tree for March 24 (iwlwifi) Randy Dunlap
2010-03-24 21:23 ` [PATCH] iwlwifi: fix build error for CONFIG_IWLAGN=n John W. Linville
[not found] ` <1269465799-19060-1-git-send-email-linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2010-03-24 21:33 ` Johannes Berg
2010-03-24 21:33 ` Johannes Berg
2010-03-24 21:42 ` reinette chatre
2010-03-24 22:37 ` John W. Linville
2010-03-24 22:37 ` John W. Linville
2010-03-24 22:41 ` reinette chatre
2010-03-24 23:38 ` John W. Linville
2010-03-25 16:33 ` reinette chatre
2010-03-24 22:59 ` 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=4BAB8362.7030005@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=forest@alittletooquiet.net \
--cc=gregkh@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.