public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Luka Gejak <luka.gejak@linux.dev>
To: shyamsunderreddypadira@gmail.com
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	linux-staging@lists.linux.dev, luka.gejak@linux.dev
Subject: Re: [PATCH] staging: rtl8723bs: hal: add blank line after declaration
Date: Tue, 28 Apr 2026 08:56:32 +0200	[thread overview]
Message-ID: <17A9C473-E8DD-4CDF-B2F6-4EA5D0C4E5C1@linux.dev> (raw)
In-Reply-To: <20260427183456.6160-1-shyamsunderreddypadira@gmail.com>

> Add missing  blank line after variable declarations to comply with
> kernel coding style.
> 
> Signed-off-by: Shyam Sunder Reddy Padira <shyamsunderreddypadira@gmail.com>
> ---
>  drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c b/drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c
> index 6d5e531505f9..7fac1c2ba8e0 100644
> --- a/drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c
> +++ b/drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c
> @@ -575,6 +575,7 @@ static void phy_SetRegBW_8723B(
>  )
>  {
>  	u16 RegRfMod_BW, u2tmp = 0;
> +
>  	RegRfMod_BW = rtw_read16(Adapter, REG_TRXPTCL_CTL_8723B);
>  
>  	switch (CurrentBW) {
> -- 
> 2.43.0
>

Hi Shyam,
I am sorry to inform you but someone has does this change already in 
the past. You are probably working on mainline or older tree, which is
why this change wasn't present for you. Please work on top of 
staging-next branch in the future.
Best regards,
Luka Gejak

  reply	other threads:[~2026-04-28  6:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 18:34 [PATCH] staging: rtl8723bs: hal: add blank line after declaration Shyam Sunder Reddy Padira
2026-04-28  6:56 ` Luka Gejak [this message]
2026-05-04 14:48 ` Greg KH

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=17A9C473-E8DD-4CDF-B2F6-4EA5D0C4E5C1@linux.dev \
    --to=luka.gejak@linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=shyamsunderreddypadira@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