linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: reinette chatre <reinette.chatre@intel.com>
To: "subrata@linux.vnet.ibm.com" <subrata@linux.vnet.ibm.com>
Cc: sachinp <sachinp@linux.vnet.ibm.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>, Greg KH <greg@kroah.com>,
	Andrea Merello <andreamrl@tiscali.it>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Linuxppc-dev <Linuxppc-dev@ozlabs.org>,
	linux-next <linux-next@vger.kernel.org>,
	Alexander Beregalov <a.beregalov@gmail.com>,
	"James P. Ketrenos" <ipw2100-admin@linux.intel.com>
Subject: Re: [Ipw2100-admin] [BUILD FAILURE 04/12] Next April 14 : PPC64 randconfig [drivers/staging/built-in.o]
Date: Tue, 14 Apr 2009 11:59:55 -0700	[thread overview]
Message-ID: <1239735595.15115.60.camel@rc-desk> (raw)
In-Reply-To: <1239733717.5344.76.camel@subratamodak.linux.ibm.com>

Hi Subrata,

On Tue, 2009-04-14 at 11:28 -0700, Subrata Modak wrote:
> Observed the following build error:
> ---
> LD      drivers/built-in.o
> drivers/staging/built-in.o: In function `ieee80211_xmit':
> drivers/staging/rtl8187se/ieee80211/ieee80211_tx.c:528: multiple
> definition of `ieee80211_xmit'
> drivers/net/built-in.o:drivers/net/wireless/ipw2x00/libipw_tx.c:256:
> first defined here
> make[1]: *** [drivers/built-in.o] Error 1
> make: *** [drivers] Error 2

Looks like the rtl8187se driver started with a copy of ipw2x00's
library. Errors like this can thus be expected and should be addressed
by rtl8187se as they are the ones who made the copy.

Reinette

  reply	other threads:[~2009-04-14 18:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14 18:28 [BUILD FAILURE 04/12] Next April 14 : PPC64 randconfig [drivers/staging/built-in.o] Subrata Modak
2009-04-14 18:59 ` reinette chatre [this message]
2009-04-15  1:06   ` [Ipw2100-admin] " 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=1239735595.15115.60.camel@rc-desk \
    --to=reinette.chatre@intel.com \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=a.beregalov@gmail.com \
    --cc=andreamrl@tiscali.it \
    --cc=greg@kroah.com \
    --cc=ipw2100-admin@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=sachinp@linux.vnet.ibm.com \
    --cc=sfr@canb.auug.org.au \
    --cc=subrata@linux.vnet.ibm.com \
    /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).