All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Siwanan Bungtong <horstaufmental@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
	straube.linux@gmail.com, ignacio.pena87@gmail.com
Subject: Re: [PATCH 1/2] staging: rtl8723bs: add braces to if/else arms in rtw_efuse.c
Date: Mon, 4 May 2026 16:52:38 +0200	[thread overview]
Message-ID: <2026050433-cube-shrubs-9d80@gregkh> (raw)
In-Reply-To: <20260501203121.227992-2-horstaufmental@gmail.com>

On Sat, May 02, 2026 at 03:31:20AM +0700, Siwanan Bungtong wrote:
> Add missing braces to if/else statements to comply with kernel
> coding style and improve readability.
> 
> No functional changes.
> 
> Signed-off-by: Siwanan Bungtong <horstaufmental@gmail.com>
> ---
>  drivers/staging/rtl8723bs/core/rtw_efuse.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/staging/rtl8723bs/core/rtw_efuse.c b/drivers/staging/rtl8723bs/core/rtw_efuse.c
> index 099320e4eb50..7600b723fda3 100644
> --- a/drivers/staging/rtl8723bs/core/rtw_efuse.c
> +++ b/drivers/staging/rtl8723bs/core/rtw_efuse.c
> @@ -76,9 +76,9 @@ u16		Address)
>  				break;
>  		}
>  		return rtw_read8(Adapter, EFUSE_CTRL);
> -	} else
> +	} else {
>  		return 0xFF;
> -
> +	}
>  } /* EFUSE_Read1Byte */
>  
>  /*  11/16/2008 MH Read one byte from real Efuse. */
> -- 
> 2.53.0
> 
> 

Does not apply to my tree :(

  reply	other threads:[~2026-05-04 14:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-01 20:31 [PATCH 0/2] staging: rtl8723bs: add braces to if/else statements Siwanan Bungtong
2026-05-01 20:31 ` [PATCH 1/2] staging: rtl8723bs: add braces to if/else arms in rtw_efuse.c Siwanan Bungtong
2026-05-04 14:52   ` Greg KH [this message]
2026-05-01 20:31 ` [PATCH 2/2] staging: rtl8723bs: add braces to if/else arms in HalBtc8723b1Ant.c Siwanan Bungtong
2026-05-04 12:33 ` [PATCH 0/2] staging: rtl8723bs: add braces to if/else statements Nikolay Kulikov

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=2026050433-cube-shrubs-9d80@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=horstaufmental@gmail.com \
    --cc=ignacio.pena87@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=straube.linux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.