Linux kernel staging patches
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Alonso Garrigues <agarrigues@riseup.net>
Cc: error27@gmail.com, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: remove unnecessary braces in odm_HWConfig.c
Date: Tue, 7 Jul 2026 13:29:56 +0200	[thread overview]
Message-ID: <2026070742-playgroup-stoop-0128@gregkh> (raw)
In-Reply-To: <20260624193446.1429981-1-agarrigues@riseup.net>

On Wed, Jun 24, 2026 at 08:34:46PM +0100, Alonso Garrigues wrote:
> Single statement block does not need braces.
> 
> Signed-off-by: Alonso Garrigues <agarrigues@riseup.net>
> ---
>  drivers/staging/rtl8723bs/hal/odm_HWConfig.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/drivers/staging/rtl8723bs/hal/odm_HWConfig.c b/drivers/staging/rtl8723bs/hal/odm_HWConfig.c
> index c88d669cb086..1716252641d3 100644
> --- a/drivers/staging/rtl8723bs/hal/odm_HWConfig.c
> +++ b/drivers/staging/rtl8723bs/hal/odm_HWConfig.c
> @@ -236,9 +236,8 @@ static void odm_rx_phy_status_parsing(struct dm_odm_t *dm_odm,
>  	if (is_cck_rate) {
>  		phy_info->signal_strength = (u8)(odm_signal_scale_mapping(dm_odm, pwdb_all));
>  	} else {
> -		if (rf_rx_num != 0) {
> +		if (rf_rx_num != 0)
>  			phy_info->signal_strength = (u8)(odm_signal_scale_mapping(dm_odm, total_rssi /= rf_rx_num));
> -		}
>  	}
>  }
>  
> -- 
> 2.54.0
> 
> 

Someone else already submitted this change before you, sorry.

greg k-h

  reply	other threads:[~2026-07-07 11:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-24 19:34 [PATCH] staging: rtl8723bs: remove unnecessary braces in odm_HWConfig.c Alonso Garrigues
2026-07-07 11:29 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-05-24 11:17 Atharv Margur

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=2026070742-playgroup-stoop-0128@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=agarrigues@riseup.net \
    --cc=error27@gmail.com \
    --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