Linux kernel staging patches
 help / color / mirror / Atom feed
From: Atin Bainada <hi@atinb.me>
To: gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, Atin Bainada <hi@atinb.me>
Subject: [PATCH] staging: rtl8723bs: add whitespace before operator
Date: Sat, 13 May 2023 12:10:16 +0000	[thread overview]
Message-ID: <20230513120950.66944-1-hi@atinb.me> (raw)

fix the following post-commit hook checkpatch error:

spaces required around that '?' (ctx:VxW)
2278: FILE: rtl8723b_hal_init.c:2278:
+                       pHalData->ant_path = (tempval & BIT(6))? RF_PATH_B : RF_PATH_A;
                                                               ^

Signed-off-by: Atin Bainada <hi@atinb.me>
---
 drivers/staging/rtl8723bs/hal/rtl8723b_hal_init.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/rtl8723bs/hal/rtl8723b_hal_init.c b/drivers/staging/rtl8723bs/hal/rtl8723b_hal_init.c
index c3c1b49674d3..abfaf1eebf5b 100644
--- a/drivers/staging/rtl8723bs/hal/rtl8723b_hal_init.c
+++ b/drivers/staging/rtl8723bs/hal/rtl8723b_hal_init.c
@@ -2275,7 +2275,7 @@ void Hal_EfuseParseBTCoexistInfo_8723B(
 			pHalData->EEPROMBluetoothAntNum = tempval & BIT(0);
 			/*  EFUSE_0xC3[6] == 0, S1(Main)-RF_PATH_A; */
 			/*  EFUSE_0xC3[6] == 1, S0(Aux)-RF_PATH_B */
-			pHalData->ant_path = (tempval & BIT(6))? RF_PATH_B : RF_PATH_A;
+			pHalData->ant_path = (tempval & BIT(6)) ? RF_PATH_B : RF_PATH_A;
 		} else {
 			pHalData->EEPROMBluetoothAntNum = Ant_x1;
 			if (pHalData->PackageType == PACKAGE_QFN68)
-- 
2.40.0



             reply	other threads:[~2023-05-13 12:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-13 12:10 Atin Bainada [this message]
2023-05-13 12:58 ` [PATCH] staging: rtl8723bs: add whitespace before operator Greg KH
2023-05-16 10:31   ` Atin
2023-05-16 10:47     ` 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=20230513120950.66944-1-hi@atinb.me \
    --to=hi@atinb.me \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-staging@lists.linux.dev \
    /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