All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] iwlegacy: change some symbols duplicated from iwlwifi directory
Date: Fri, 25 Feb 2011 16:56:06 -0600	[thread overview]
Message-ID: <4D683386.4040407@lwfinger.net> (raw)
In-Reply-To: <1298672550.28351.113.camel@wwguy-huron>

On 02/25/2011 04:22 PM, Guy, Wey-Yi wrote:
> On Fri, 2011-02-25 at 14:05 -0800, John W. Linville wrote:
>> Sorry about the SPAM -- either I had some network issues here or I
>> _really_ meant for you to see this!! :-)
>>
>> On Fri, Feb 25, 2011 at 04:50:06PM -0500, John W. Linville wrote:
>>> drivers/net/wireless/iwlegacy/built-in.o:(.rodata+0x29f0): multiple definition of `iwl_rates'
>>> drivers/net/wireless/iwlwifi/built-in.o:(.rodata+0xa68): first defined here
>>> powerpc64-linux-ld: Warning: size of symbol `iwl_rates' changed from 143 in drivers/net/wireless/iwlwifi/built-in.o to 130 in drivers/net/wireless/iwlegacy/built-in.o
>>> drivers/net/wireless/iwlegacy/built-in.o:(.data+0x0): multiple definition of `bt_coex_active'
>>> drivers/net/wireless/iwlwifi/built-in.o:(.data+0x668): first defined here
>>> drivers/net/wireless/iwlegacy/built-in.o:(.rodata+0x750): multiple definition of `iwl_eeprom_band_1'
>>> drivers/net/wireless/iwlwifi/built-in.o:(.rodata+0x27d0): first defined here
>>> drivers/net/wireless/iwlegacy/built-in.o:(.rodata+0x3f0): multiple definition of `iwl_bcast_addr'
>>> drivers/net/wireless/iwlwifi/built-in.o:(.rodata+0x24f8): first defined here
>>> drivers/net/wireless/iwlegacy/built-in.o:(.bss+0x3d48): multiple definition of `iwl_debug_level'
>>> drivers/net/wireless/iwlwifi/built-in.o:(.bss+0x21950): first defined here
>>>
> 
> Thank you very much for fix this, we just miss it :-(

I got hit earlier in the week with a similar issue on a patch of mine. It seems
that a "make allyesconfig && make" is worthwhile whenever large changes are
made, particularly when code is being moved.

Larry

  reply	other threads:[~2011-02-25 22:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-25 21:50 [PATCH] iwlegacy: change some symbols duplicated from iwlwifi directory John W. Linville
2011-02-25 22:05 ` John W. Linville
2011-02-25 22:22   ` Guy, Wey-Yi
2011-02-25 22:56     ` Larry Finger [this message]
2011-02-26  1:47   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2011-02-25 21:32 John W. Linville
2011-02-25 21:12 John W. Linville

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=4D683386.4040407@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=sfr@canb.auug.org.au \
    --cc=wey-yi.w.guy@intel.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 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.