From: Larry Finger <Larry.Finger@lwfinger.net>
To: kvalo@codeaurora.org
Cc: linux-wireless@vger.kernel.org,
Larry Finger <Larry.Finger@lwfinger.net>,
Yan-Hsuan Chuang <yhchuang@realtek.com>,
Ping-Ke Shih <pkshih@realtek.com>,
Birming Chiu <birming@realtek.com>, Shaofu <shaofu@realtek.com>,
Steven Ting <steventing@realtek.com>
Subject: [PATCH 0/7] rtlwifi: btcoex: Final round of fixes
Date: Thu, 25 May 2017 12:48:07 -0500 [thread overview]
Message-ID: <20170525174814.25005-1-Larry.Finger@lwfinger.net> (raw)
These 7 patches finish this round of fixes for the various components
of btcoex.
Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Yan-Hsuan Chuang <yhchuang@realtek.com>
Cc: Ping-Ke Shih <pkshih@realtek.com>
Cc: Birming Chiu <birming@realtek.com>
Cc: Shaofu <shaofu@realtek.com>
Cc: Steven Ting <steventing@realtek.com>
Larry Finger (3):
rtlwifi: btcoex: Fix Sparse messages for undeclared symbols
rtlwifi: btcoex: Fix logic error in 21a 1ant
rtlwifi: btcoex: Fix another edit mistake in 21a 1ant
Yan-Hsuan Chuang (4):
rtlwifi: btcoex: update new btcoex version
rtlwifi: btcoex: fix compiler warnings for unused functions
rtlwifi: btcoex: bind bt to the adapter when initialization
rtlwifi: btcoex: 92e: rename function that was missing to be
consistent
.../realtek/rtlwifi/btcoexist/halbt_precomp.h | 22 +
.../realtek/rtlwifi/btcoexist/halbtc8192e2ant.c | 2 +-
.../realtek/rtlwifi/btcoexist/halbtc8192e2ant.h | 32 +-
.../realtek/rtlwifi/btcoexist/halbtc8723b1ant.c | 53 +-
.../realtek/rtlwifi/btcoexist/halbtc8723b1ant.h | 41 +-
.../realtek/rtlwifi/btcoexist/halbtc8723b2ant.c | 1 +
.../realtek/rtlwifi/btcoexist/halbtc8723b2ant.h | 3 +
.../realtek/rtlwifi/btcoexist/halbtc8821a1ant.c | 62 +-
.../realtek/rtlwifi/btcoexist/halbtc8821a1ant.h | 38 +-
.../realtek/rtlwifi/btcoexist/halbtc8821a2ant.c | 3 +-
.../realtek/rtlwifi/btcoexist/halbtc8821a2ant.h | 26 +-
.../realtek/rtlwifi/btcoexist/halbtcoutsrc.c | 764 +++++++++++++++------
.../realtek/rtlwifi/btcoexist/halbtcoutsrc.h | 43 +-
.../wireless/realtek/rtlwifi/btcoexist/rtl_btc.c | 36 +-
14 files changed, 747 insertions(+), 379 deletions(-)
--
2.12.0
next reply other threads:[~2017-05-25 17:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 17:48 Larry Finger [this message]
2017-05-25 17:48 ` [PATCH 1/7] rtlwifi: btcoex: update new btcoex version Larry Finger
2017-05-26 8:38 ` kbuild test robot
2017-05-26 10:05 ` kbuild test robot
2017-05-25 17:48 ` [PATCH 2/7] rtlwifi: btcoex: fix compiler warnings for unused functions Larry Finger
2017-05-25 17:48 ` [PATCH 3/7] rtlwifi: btcoex: bind bt to the adapter when initialization Larry Finger
2017-05-25 17:48 ` [PATCH 4/7] rtlwifi: btcoex: 92e: rename function that was missing to be consistent Larry Finger
2017-05-25 17:48 ` [PATCH 5/7] rtlwifi: btcoex: Fix Sparse messages for undeclared symbols Larry Finger
2017-05-25 17:48 ` [PATCH 6/7] rtlwifi: btcoex: Fix logic error in 21a 1ant Larry Finger
2017-05-25 17:48 ` [PATCH 7/7] rtlwifi: btcoex: Fix another edit mistake " Larry Finger
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=20170525174814.25005-1-Larry.Finger@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=birming@realtek.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=shaofu@realtek.com \
--cc=steventing@realtek.com \
--cc=yhchuang@realtek.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