From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: randy.dunlap@oracle.com
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: iwlwifi: fix modular legacy build errors
Date: Wed, 17 Nov 2010 08:36:37 -0800 [thread overview]
Message-ID: <1290011797.12056.255.camel@wwguy-huron> (raw)
Hi Randy,
the "iwlwifi: fix modular legacy build errors" patch cause the following
WARNING when compile
WARNING: drivers/net/wireless/iwlwifi/iwlagn:
'iwl_legacy_tx_cmd_protection' exported twice. Previous export was in
drivers/net/wireless/iwlwifi/iwl3945.ko
WARNING: drivers/net/wireless/iwlwifi/iwlagn: 'iwl_isr_legacy' exported
twice. Previous export was in drivers/net/wireless/iwlwifi/iwl3945.ko
WARNING: drivers/net/wireless/iwlwifi/iwlagn:
'iwl_legacy_mac_bss_info_changed' exported twice. Previous export was in
drivers/net/wireless/iwlwifi/iwl3945.ko
WARNING: drivers/net/wireless/iwlwifi/iwlagn: 'iwl_legacy_mac_reset_tsf'
exported twice. Previous export was in
drivers/net/wireless/iwlwifi/iwl3945.ko
WARNING: drivers/net/wireless/iwlwifi/iwlagn: 'iwl_legacy_mac_config'
exported twice. Previous export was in
drivers/net/wireless/iwlwifi/iwl3945.ko
The .config option are
#
# Debugging Options
#
CONFIG_IWLWIFI_DEBUG=y
CONFIG_IWLWIFI_DEBUGFS=y
CONFIG_IWLWIFI_DEVICE_TRACING=y
CONFIG_IWLAGN=m
CONFIG_IWL4965=y
CONFIG_IWL5000=y
CONFIG_IWL3945=m
Wey
next reply other threads:[~2010-11-17 16:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 16:36 Guy, Wey-Yi [this message]
2010-11-17 16:49 ` iwlwifi: fix modular legacy build errors Johannes Berg
2010-11-17 17:12 ` Randy Dunlap
2010-11-17 17:11 ` Guy, Wey-Yi
2010-11-18 17:11 ` Randy Dunlap
2010-11-18 17:36 ` Guy, Wey-Yi
2010-11-18 17:54 ` John W. Linville
2010-11-18 19:29 ` Randy Dunlap
2010-11-18 19:46 ` Johannes Berg
2010-11-18 19:55 ` Randy Dunlap
2010-11-18 20:03 ` Johannes Berg
2010-11-17 17:06 ` Please revert "iwlwifi: fix modular legacy build errors" patch Guy, Wey-Yi
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=1290011797.12056.255.camel@wwguy-huron \
--to=wey-yi.w.guy@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=randy.dunlap@oracle.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.