From: "John W. Linville" <linville@tuxdriver.com>
To: Felix Fietkau <nbd@openwrt.org>
Cc: linux-wireless@vger.kernel.org, mcgrof@qca.qualcomm.com
Subject: Re: [PATCH] ath9k_hw: make bluetooth coexistence support optional at compile time
Date: Tue, 13 Dec 2011 15:28:13 -0500 [thread overview]
Message-ID: <20111213202813.GC2613@tuxdriver.com> (raw)
In-Reply-To: <1323550849-16651-1-git-send-email-nbd@openwrt.org>
On Sat, Dec 10, 2011 at 10:00:49PM +0100, Felix Fietkau wrote:
> Many systems (e.g. embedded systems) do not have wifi modules connected to
> bluetooth modules, so bluetooth coexistence is irrelevant there. With the
> addition of MCI support, ath9k picked up quite a bit of extra code that
> can be compiled out this way.
>
> This patch redefines ATH9K_HW_CAP_MCI and adds an inline wrapper for
> querying the bluetooth coexistence scheme, allowing the compiler to
> eliminate code that uses it, with only very little use of #ifdef.
>
> On MIPS this reduces the total size for the modules by about 20k.
>
> Signed-off-by: Felix Fietkau <nbd@openwrt.org>
CC [M] drivers/net/wireless/ath/ath9k/beacon.o
In file included from drivers/net/wireless/ath/ath9k/hw.h:30:0,
from drivers/net/wireless/ath/ath9k/debug.h:20,
from drivers/net/wireless/ath/ath9k/ath9k.h:26,
from drivers/net/wireless/ath/ath9k/beacon.c:18:
drivers/net/wireless/ath/ath9k/btcoex.h: In function ‘ath9k_hw_get_btcoex_scheme’:
drivers/net/wireless/ath/ath9k/btcoex.h:105:11: error: dereferencing pointer to incomplete type
Did I miss a patch?
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2011-12-13 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-10 21:00 [PATCH] ath9k_hw: make bluetooth coexistence support optional at compile time Felix Fietkau
2011-12-11 4:20 ` Julian Calaby
2011-12-11 9:52 ` Felix Fietkau
2011-12-13 20:28 ` John W. Linville [this message]
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=20111213202813.GC2613@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@qca.qualcomm.com \
--cc=nbd@openwrt.org \
/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).