From: Jagath Jog J <jagathjog1996@gmail.com>
To: gregkh@linuxfoundation.org, hdegoede@redhat.com,
Larry.Finger@lwfinger.net
Cc: fabioaiuto83@gmail.com, dan.carpenter@oracle.com,
marcocesati@gmail.com, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, jagathjog1996@gmail.com
Subject: [Patch 3/3] Staging: rtl8723bs: Inserting blank line after declaration
Date: Mon, 24 Jan 2022 09:14:56 +0530 [thread overview]
Message-ID: <20220124034456.8665-4-jagathjog1996@gmail.com> (raw)
In-Reply-To: <20220124034456.8665-1-jagathjog1996@gmail.com>
Fix following checkpatch.pl warning by inserting blank line
WARNING: Missing a blank line after declarations
Signed-off-by: Jagath Jog J <jagathjog1996@gmail.com>
---
drivers/staging/rtl8723bs/hal/hal_intf.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/drivers/staging/rtl8723bs/hal/hal_intf.c b/drivers/staging/rtl8723bs/hal/hal_intf.c
index 4868a69cdb8f..94ecefb9113d 100644
--- a/drivers/staging/rtl8723bs/hal/hal_intf.c
+++ b/drivers/staging/rtl8723bs/hal/hal_intf.c
@@ -181,6 +181,7 @@ void rtw_hal_disable_interrupt(struct adapter *padapter)
u8 rtw_hal_check_ips_status(struct adapter *padapter)
{
u8 val = false;
+
if (padapter->HalFunc.check_ips_status)
val = padapter->HalFunc.check_ips_status(padapter);
@@ -209,6 +210,7 @@ s32 rtw_hal_xmit(struct adapter *padapter, struct xmit_frame *pxmitframe)
s32 rtw_hal_mgnt_xmit(struct adapter *padapter, struct xmit_frame *pmgntframe)
{
s32 ret = _FAIL;
+
update_mgntframe_attrib_addr(padapter, pmgntframe);
/* pframe = (u8 *)(pmgntframe->buf_addr) + TXDESC_OFFSET; */
/* pwlanhdr = (struct rtw_ieee80211_hdr *)pframe; */
@@ -299,6 +301,7 @@ void rtw_hal_stop_thread(struct adapter *padapter)
u32 rtw_hal_read_bbreg(struct adapter *padapter, u32 RegAddr, u32 BitMask)
{
u32 data = 0;
+
if (padapter->HalFunc.read_bbreg)
data = padapter->HalFunc.read_bbreg(padapter, RegAddr, BitMask);
return data;
@@ -312,6 +315,7 @@ void rtw_hal_write_bbreg(struct adapter *padapter, u32 RegAddr, u32 BitMask, u32
u32 rtw_hal_read_rfreg(struct adapter *padapter, u32 eRFPath, u32 RegAddr, u32 BitMask)
{
u32 data = 0;
+
if (padapter->HalFunc.read_rfreg)
data = padapter->HalFunc.read_rfreg(padapter, eRFPath, RegAddr, BitMask);
return data;
@@ -385,6 +389,7 @@ bool rtw_hal_c2h_valid(struct adapter *adapter, u8 *buf)
s32 rtw_hal_c2h_handler(struct adapter *adapter, u8 *c2h_evt)
{
s32 ret = _FAIL;
+
if (adapter->HalFunc.c2h_handler)
ret = adapter->HalFunc.c2h_handler(adapter, c2h_evt);
return ret;
--
2.17.1
next prev parent reply other threads:[~2022-01-24 3:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 3:44 [Patch 0/3] Staging: rtl8723bs: Fix codestyle errors and warnings Jagath Jog J
2022-01-24 3:44 ` [Patch 1/3] Staging: rtl8723bs: Placing opening { braces in previous line Jagath Jog J
2022-01-25 17:22 ` Joe Perches
2022-01-24 3:44 ` [Patch 2/3] Staging: rtl8723bs: Removed extra spaces between datatype and variable Jagath Jog J
2022-01-24 3:44 ` Jagath Jog J [this message]
2022-01-24 8:16 ` [Patch 0/3] Staging: rtl8723bs: Fix codestyle errors and warnings Hans de Goede
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=20220124034456.8665-4-jagathjog1996@gmail.com \
--to=jagathjog1996@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=dan.carpenter@oracle.com \
--cc=fabioaiuto83@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=marcocesati@gmail.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
Powered by JetHome