From: Dan Carpenter <error27@gmail.com>
To: Subhrojyoti Bala <subhrojyoti0609@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] staging: rtl8723bs: Fix coding style issues in header files
Date: Tue, 16 Jun 2026 15:21:10 +0300 [thread overview]
Message-ID: <ajE_thze3242HVdP@stanley.mountain> (raw)
In-Reply-To: <20260616110048.45541-1-subhrojyoti0609@gmail.com>
On Tue, Jun 16, 2026 at 04:30:43PM +0530, Subhrojyoti Bala wrote:
> This patch series fixes various coding style issues in the
> rtl8723bs staging driver header files, as reported by
> checkpatch.pl:
>
> - Fix multi-line comment style in wlan_bssdef.h
> - Fix enum indentation in rtw_mlme.h
> - Fix block comment style in rtw_mlme.h
> - Fix multi-line comment style in rtw_mlme.h
> - Fix whitespace in comments in rtw_mlme.h
>
combine patches 1,3-5 since they're all basically the same sort
of patch in the same driver and they're pretty small.
Wait for a day before resending.
https://staticthinking.wordpress.com/2022/07/27/how-to-send-a-v2-patch/
regards,
dan carpenter
prev parent reply other threads:[~2026-06-16 12:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 11:00 [PATCH 0/5] staging: rtl8723bs: Fix coding style issues in header files Subhrojyoti Bala
2026-06-16 11:00 ` [PATCH 1/5] staging: rtl8723bs: Fix multi-line comment style in wlan_bssdef.h Subhrojyoti Bala
2026-06-16 11:00 ` [PATCH 2/5] staging: rtl8723bs: Fix indentation in enum in rtw_mlme.h Subhrojyoti Bala
2026-06-16 11:00 ` [PATCH 3/5] staging: rtl8723bs: Fix block comment style " Subhrojyoti Bala
2026-06-16 11:00 ` [PATCH 4/5] staging: rtl8723bs: Fix multi-line " Subhrojyoti Bala
2026-06-16 11:00 ` [PATCH 5/5] staging: rtl8723bs: Fix whitespace in comments " Subhrojyoti Bala
2026-06-16 12:09 ` [PATCH 0/5] staging: rtl8723bs: Fix coding style issues in header files Greg Kroah-Hartman
2026-06-16 12:21 ` 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=ajE_thze3242HVdP@stanley.mountain \
--to=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=subhrojyoti0609@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.