From: Vasanthakumar Thiagarajan <vasanth@atheros.com>
To: Luis Rodriguez <lrodriguez@atheros.com>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
Luis Rodriguez <Luis.Rodriguez@Atheros.com>
Subject: Re: [PATCH 09/15] ath9k: remove unused bt_duty_cycle
Date: Thu, 10 Sep 2009 10:31:07 +0530 [thread overview]
Message-ID: <20090910050106.GH4166@vasanth-laptop> (raw)
In-Reply-To: <1252539901-20679-10-git-send-email-lrodriguez@atheros.com>
On Thu, Sep 10, 2009 at 05:14:55AM +0530, Luis Rodriguez wrote:
> Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
> ---
> drivers/net/wireless/ath/ath9k/btcoex.h | 1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath9k/btcoex.h b/drivers/net/wireless/ath/ath9k/btcoex.h
> index d932f01..72c613d 100644
> --- a/drivers/net/wireless/ath/ath9k/btcoex.h
> +++ b/drivers/net/wireless/ath/ath9k/btcoex.h
> @@ -61,7 +61,6 @@ struct ath_btcoex_info {
> u8 wlanactive_gpio;
> u8 btactive_gpio;
> u8 btpriority_gpio;
> - u8 bt_duty_cycle; /* BT duty cycle in percentage */
> u32 bt_coex_mode; /* Register setting for AR_BT_COEX_MODE */
> u32 bt_coex_weights; /* Register setting for AR_BT_COEX_WEIGHT */
> u32 bt_coex_mode2; /* Register setting for AR_BT_COEX_MODE2 */
> --
thanks.
Vasanth
next prev parent reply other threads:[~2009-09-10 5:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 23:44 [PATCH 00/15] ath9k: cleanups to help other core drivers Luis R. Rodriguez
2009-09-09 23:44 ` [PATCH 01/15] ath9k: use ath_hw for DPRINTF() and debug init/exit Luis R. Rodriguez
2009-09-09 23:44 ` [PATCH 02/15] ath9k: move btcoex core driver info to its own struct Luis R. Rodriguez
2009-09-09 23:44 ` [PATCH 03/15] ath9k: move hw specific btcoex info to ath_hw Luis R. Rodriguez
2009-09-09 23:44 ` [PATCH 04/15] ath9k: split bluetooth hardware coex init into two helpers Luis R. Rodriguez
2009-09-09 23:44 ` [PATCH 05/15] ath9k: move driver core helpers to main.c Luis R. Rodriguez
2009-09-09 23:44 ` [PATCH 06/15] ath9k: split ath9k_hw_btcoex_enable() into two helpers Luis R. Rodriguez
2009-09-09 23:44 ` [PATCH 07/15] ath9k: replaces SC_OP_BTCOEX_ENABLED with a bool Luis R. Rodriguez
2009-09-09 23:44 ` [PATCH 08/15] ath9k: move bt_stomp_type to driver core Luis R. Rodriguez
2009-09-09 23:44 ` [PATCH 09/15] ath9k: remove unused bt_duty_cycle Luis R. Rodriguez
2009-09-10 5:01 ` Vasanthakumar Thiagarajan [this message]
2009-09-09 23:44 ` [PATCH 10/15] ath9k: rename btcoex_scheme to just scheme Luis R. Rodriguez
2009-09-09 23:44 ` [PATCH 11/15] ath9k: rename ath_btcoex_info to ath_btcoex_hw Luis R. Rodriguez
2009-09-09 23:44 ` [PATCH 12/15] ath9k: simplify ath_btcoex_bt_stomp() Luis R. Rodriguez
2009-09-09 23:44 ` [PATCH 13/15] ath9k: now move ath9k_hw_btcoex_set_weight() to btcoex.c Luis R. Rodriguez
2009-09-09 23:45 ` [PATCH 14/15] ath9k: move ath_btcoex_config and ath_bt_mode " Luis R. Rodriguez
2009-09-09 23:45 ` [PATCH 15/15] ath9k: rename ath_btcoex_supported() to ath9k_hw_btcoex_supported() Luis R. Rodriguez
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=20090910050106.GH4166@vasanth-laptop \
--to=vasanth@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=devel@linuxdriverproject.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.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).