From: Greg KH <gregkh@linuxfoundation.org>
To: Moksh Panicker <mokshpanicker.7@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: remove blank line after open brace in hal_com.c
Date: Mon, 4 May 2026 11:28:30 +0200 [thread overview]
Message-ID: <2026050434-unleveled-syrup-5ae1@gregkh> (raw)
In-Reply-To: <20260503181646.54816-1-mokshpanicker.7@gmail.com>
On Sun, May 03, 2026 at 06:16:46PM +0000, Moksh Panicker wrote:
> Remove unnecessary blank line after the opening brace of a for loop.
> This fixes the following checkpatch.pl warning:
>
> CHECK: Blank lines aren't necessary after an open brace '{'
> Signed-off-by: Moksh Panicker <mokshpanicker.7@gmail.com>
> ---
> drivers/staging/rtl8723bs/hal/hal_com.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/staging/rtl8723bs/hal/hal_com.c b/drivers/staging/rtl8723bs/hal/hal_com.c
> index b4b135a9ca22..3c85e96ec57d 100644
> --- a/drivers/staging/rtl8723bs/hal/hal_com.c
> +++ b/drivers/staging/rtl8723bs/hal/hal_com.c
> @@ -252,7 +252,6 @@ void HalSetBrateCfg(struct adapter *Adapter, u8 *mBratesOS, u16 *pBrateCfg)
> u8 i, is_brate, brate;
>
> for (i = 0; i < NDIS_802_11_LENGTH_RATES_EX; i++) {
> -
> is_brate = mBratesOS[i] & IEEE80211_BASIC_RATE_MASK;
> brate = mBratesOS[i] & 0x7f;
>
> --
> 2.34.1
>
For all of your patches you are not sending them to the staging mailing
list, why not? What kernel version are you working off of that shows
the driverdev mailing list as still alive?
Please resend all of your submitted patches to the list that
scripts/get_maintainer.pl shows to send to, as a patch series, and we
will be glad to review them there.
thanks,
greg k-h
prev parent reply other threads:[~2026-05-04 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-03 18:16 [PATCH] staging: rtl8723bs: remove blank line after open brace in hal_com.c Moksh Panicker
2026-05-04 9:28 ` 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=2026050434-unleveled-syrup-5ae1@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mokshpanicker.7@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