public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Bragatheswaran Manickavel <bragathemanick0908@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: hal: Fix codespell-reported spelling mistakes
Date: Tue, 19 Sep 2023 22:43:42 +0530	[thread overview]
Message-ID: <7bad2536-087e-9ecd-36a5-b243e0b3e1e9@gmail.com> (raw)
In-Reply-To: <20230917134940.2746-1-bragathemanick0908@gmail.com>


On 17/09/23 19:19, Bragatheswaran Manickavel wrote:
 >They are appear to be spelling mistakes,
 >Initially identified in a codespell report and never been addressed so 
far.
 >
 >./rtl8723b_phycfg.c:156: Threre ==> There, three
 >./rtl8723b_phycfg.c:283: Condig ==> Config
 >./rtl8723b_phycfg.c:328: Tranceiver ==> Transceiver
 >
 >Signed-off-by: Bragatheswaran Manickavel <bragathemanick0908@gmail.com>
 >---
 > drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c | 6 +++---
 > 1 file changed, 3 insertions(+), 3 deletions(-)
 >
 >diff --git a/drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c 
b/drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c
 >index a3bff27af523..7764896a04ea 100644
 >--- a/drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c
 >+++ b/drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c
 >@@ -153,7 +153,7 @@ static u32 phy_RFSerialRead_8723B(
 >  * @Data:    The new register Data in the target bit position
 >  *            of the target to be read
 >  *
 >- * .. Note::    Threre are three types of serial operations:
 >+ * .. Note::    There are three types of serial operations:
 >  *        1. Software serial write
 >  *        2. Hardware LSSI-Low Speed Serial Interface
 >  *        3. Hardware HSSI-High speed
 >@@ -280,7 +280,7 @@ void PHY_SetRFReg_8723B(
 >
 >
 > 
/*-----------------------------------------------------------------------------
 >- * PHY_MACConfig8192C - Condig MAC by header file or parameter file.
 >+ * PHY_MACConfig8192C - Config MAC by header file or parameter file.
 >  *
 >  * Revised History:
 >  *  When        Who        Remark
 >@@ -325,7 +325,7 @@ static void phy_InitBBRFRegisterDefinition(struct 
adapter *Adapter)
 >     pHalData->PHYRegDef[RF_PATH_A].rfHSSIPara2 = 
rFPGA0_XA_HSSIParameter2;  /* wire control parameter2 */
 >     pHalData->PHYRegDef[RF_PATH_B].rfHSSIPara2 = 
rFPGA0_XB_HSSIParameter2;  /* wire control parameter2 */
 >
 >-    /*  Tranceiver Readback LSSI/HSPI mode */
 >+    /*  Transceiver Readback LSSI/HSPI mode */
 >     pHalData->PHYRegDef[RF_PATH_A].rfLSSIReadBack = 
rFPGA0_XA_LSSIReadBack;
 >     pHalData->PHYRegDef[RF_PATH_B].rfLSSIReadBack = 
rFPGA0_XB_LSSIReadBack;
 >     pHalData->PHYRegDef[RF_PATH_A].rfLSSIReadBackPi = 
TransceiverA_HSPI_Readback;
 >

Gentle remainder

Thanks,
Bragathe

  reply	other threads:[~2023-09-19 17:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-17 13:49 [PATCH] staging: rtl8723bs: hal: Fix codespell-reported spelling mistakes Bragatheswaran Manickavel
2023-09-19 17:13 ` Bragatheswaran Manickavel [this message]
     [not found] ` <CAHZF+VZVBkRP6D4xJEhoqKmr9MbjNFJ8A0NZXSwDEMFJhqBc-w@mail.gmail.com>
2023-09-19 19:05   ` Greg KH
2023-09-19 19:31     ` Bragatheswaran Manickavel

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=7bad2536-087e-9ecd-36a5-b243e0b3e1e9@gmail.com \
    --to=bragathemanick0908@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.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