From: An Ha <zero579911@gmail.com>
To: gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
An Ha <zero579911@gmail.com>
Subject: [PATCH 08/12] Staging: rtl8821ae: hal_bt_coexist: fix coding style issue
Date: Mon, 1 Sep 2014 20:29:32 -0400 [thread overview]
Message-ID: <1409617776-30730-8-git-send-email-zero579911@gmail.com> (raw)
In-Reply-To: <1409617776-30730-1-git-send-email-zero579911@gmail.com>
Fix coding style issue where the if statement unnecessarily uses curly
braces for one line statements.
Signed-off-by: An Ha <zero579911@gmail.com>
---
drivers/staging/rtl8821ae/rtl8821ae/hal_bt_coexist.c | 15 ++++++---------
1 file changed, 6 insertions(+), 9 deletions(-)
diff --git a/drivers/staging/rtl8821ae/rtl8821ae/hal_bt_coexist.c b/drivers/staging/rtl8821ae/rtl8821ae/hal_bt_coexist.c
index 938c98a..f1cf373 100644
--- a/drivers/staging/rtl8821ae/rtl8821ae/hal_bt_coexist.c
+++ b/drivers/staging/rtl8821ae/rtl8821ae/hal_bt_coexist.c
@@ -78,17 +78,15 @@ struct rtl_phy *rtlphy = &(rtlpriv->phy);
if (rtlpriv->link_info.b_busytraffic) {
rtlpcipriv->btcoexist.current_state &= ~BT_COEX_STATE_WIFI_IDLE;
- if (rtlpriv->link_info.b_tx_busy_traffic) {
+ if (rtlpriv->link_info.b_tx_busy_traffic)
rtlpcipriv->btcoexist.current_state |= BT_COEX_STATE_WIFI_UPLINK;
- } else {
+ else
rtlpcipriv->btcoexist.current_state &= ~BT_COEX_STATE_WIFI_UPLINK;
- }
- if (rtlpriv->link_info.b_rx_busy_traffic) {
+ if (rtlpriv->link_info.b_rx_busy_traffic)
rtlpcipriv->btcoexist.current_state |= BT_COEX_STATE_WIFI_DOWNLINK;
- } else {
+ else
rtlpcipriv->btcoexist.current_state &= ~BT_COEX_STATE_WIFI_DOWNLINK;
- }
} else {
rtlpcipriv->btcoexist.current_state |= BT_COEX_STATE_WIFI_IDLE;
rtlpcipriv->btcoexist.current_state &= ~BT_COEX_STATE_WIFI_UPLINK;
@@ -111,12 +109,11 @@ if (rtlpriv->mac80211.mode == WIRELESS_MODE_G
}
}
-if (bt_operation_on) {
+if (bt_operation_on)
rtlpcipriv->btcoexist.current_state |= BT_COEX_STATE_BT30;
-} else {
+else
rtlpcipriv->btcoexist.current_state &= ~BT_COEX_STATE_BT30;
}
-}
u8 rtl8821ae_dm_bt_check_coex_rssi_state1(struct ieee80211_hw *hw,
--
2.1.0
next prev parent reply other threads:[~2014-09-02 0:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 0:29 [PATCH 01/12] Staging: rtl8821ae: hal_bt_coexist: fix commenting style An Ha
2014-09-02 0:29 ` [PATCH 02/12] Staging: rtl8821ae: hal_bt_coexist: fix coding style issue An Ha
2014-09-02 0:29 ` [PATCH 03/12] " An Ha
2014-09-02 0:29 ` [PATCH 04/12] " An Ha
2014-09-02 0:29 ` [PATCH 05/12] Staging: rtl8821ae: hal_bt_coexist: fix pointer placement " An Ha
2014-09-02 0:29 ` [PATCH 06/12] Staging: rtl8821ae: hal_bt_coexist: fix " An Ha
2014-09-02 0:29 ` [PATCH 07/12] " An Ha
2014-09-02 0:29 ` An Ha [this message]
2014-09-02 0:29 ` [PATCH 09/12] " An Ha
2014-09-02 0:29 ` [PATCH 10/12] " An Ha
2014-09-02 0:29 ` [PATCH 11/12] " An Ha
2014-09-02 0:29 ` [PATCH 12/12] " An Ha
2014-09-02 9:19 ` [PATCH 01/12] Staging: rtl8821ae: hal_bt_coexist: fix commenting style Dan Carpenter
2014-09-02 11:22 ` An Tuan Ha
2014-09-02 13:35 ` Dan Carpenter
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=1409617776-30730-8-git-send-email-zero579911@gmail.com \
--to=zero579911@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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).