From: Greg KH <gregkh@linuxfoundation.org>
To: Wiktor Grzywacz <wiktor.grzywacz@3mdeb.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: fix checkpatch no spaces before tabs warning
Date: Sun, 12 Nov 2023 20:33:51 -0500 [thread overview]
Message-ID: <2023111255-flaccid-derby-b7b3@gregkh> (raw)
In-Reply-To: <20231112185710.101990-1-wiktor.grzywacz@3mdeb.com>
On Sun, Nov 12, 2023 at 07:57:10PM +0100, Wiktor Grzywacz wrote:
> There is some old commented out code, that triggers
> a checkpatch.pl no spaces before tabs warning.
>
> Signed-off-by: Wiktor Grzywacz <wiktor.grzywacz@3mdeb.com>
> ---
> drivers/staging/rtl8723bs/hal/rtl8723b_dm.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/staging/rtl8723bs/hal/rtl8723b_dm.c b/drivers/staging/rtl8723bs/hal/rtl8723b_dm.c
> index 2028791988e7..eb4e4f44d4cb 100644
> --- a/drivers/staging/rtl8723bs/hal/rtl8723b_dm.c
> +++ b/drivers/staging/rtl8723bs/hal/rtl8723b_dm.c
> @@ -46,7 +46,6 @@ static void Init_ODM_ComInfo_8723b(struct adapter *Adapter)
> ODM_CmnInfoInit(pDM_Odm, ODM_CMNINFO_CUT_VER, cut_ver);
>
> ODM_CmnInfoInit(pDM_Odm, ODM_CMNINFO_PATCH_ID, pHalData->CustomerID);
> - /* ODM_CMNINFO_BINHCT_TEST only for MP Team */
> ODM_CmnInfoInit(pDM_Odm, ODM_CMNINFO_BWIFI_TEST, Adapter->registrypriv.wifi_spec);
Deleting that commit seems odd, why did you do that? why not just fix
this properly?
>
> pdmpriv->InitODMFlag = ODM_RF_CALIBRATION|ODM_RF_TX_PWR_TRACK;
> @@ -83,8 +82,6 @@ static void Update_ODM_ComInfo_8723b(struct adapter *Adapter)
> /* */
> /* Pointer reference */
> /* */
> - /* ODM_CMNINFO_MAC_PHY_MODE pHalData->MacPhyMode92D */
> - /* ODM_CmnInfoHook(pDM_Odm, ODM_CMNINFO_MAC_PHY_MODE,&(pDM_Odm->u8_temp)); */
Why delete one comment and then one line of commented out code?
thanks,
greg k-h
prev parent reply other threads:[~2023-11-13 1:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 18:57 [PATCH] staging: rtl8723bs: fix checkpatch no spaces before tabs warning Wiktor Grzywacz
2023-11-13 1:33 ` Greg KH [this message]
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=2023111255-flaccid-derby-b7b3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=wiktor.grzywacz@3mdeb.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