From: Dan Carpenter <error27@gmail.com>
To: Vitaliy Slivinskiy <phant0m.mail2023@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: clean up coding style in sdio_intf.c
Date: Fri, 29 May 2026 10:44:59 +0300 [thread overview]
Message-ID: <ahlD-3VO5EbmtJ9_@stanley.mountain> (raw)
In-Reply-To: <20260528184415.63810-1-phant0m.mail2023@gmail.com>
On Thu, May 28, 2026 at 09:44:15PM +0300, Vitaliy Slivinskiy wrote:
> Fix checkpatch.pl warnings: remove unnecessary braces for single statement blocks, fix spacing around conditional operators, and remove multiple blank lines.
>
Work against the staging-next tree.
Split this up into multiple patches.
Run your patch through checkpatch.
> Signed-off-by: Vitaliy Slivinskiy <phant0m.mail2023@gmail.com>
> ---
> drivers/staging/rtl8723bs/os_dep/sdio_intf.c | 18 ++++++------------
> 1 file changed, 6 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/staging/rtl8723bs/os_dep/sdio_intf.c b/drivers/staging/rtl8723bs/os_dep/sdio_intf.c
> index d0feb28b7..17829b982 100644
> --- a/drivers/staging/rtl8723bs/os_dep/sdio_intf.c
> +++ b/drivers/staging/rtl8723bs/os_dep/sdio_intf.c
> @@ -19,7 +19,7 @@ static const struct sdio_device_id sdio_ids[] = {
> { SDIO_DEVICE(0x024c, 0x0626), },
> { SDIO_DEVICE(0x024c, 0x0627), },
> { SDIO_DEVICE(0x024c, 0xb723), },
> - { /* end: all zeroes */ },
> + { /* end: all zeroes */ },
This should just be:
{ }
No comment because it's obvious. No comma on the end because
nothing can be added after a sentinal.
> };
> MODULE_DEVICE_TABLE(sdio, sdio_ids);
regards,
dan carpenter
prev parent reply other threads:[~2026-05-29 7:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 18:44 [PATCH] staging: rtl8723bs: clean up coding style in sdio_intf.c Vitaliy Slivinskiy
2026-05-29 7:44 ` Dan Carpenter [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=ahlD-3VO5EbmtJ9_@stanley.mountain \
--to=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=phant0m.mail2023@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