From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Sayyad Abid <sayyad.abid16@gmail.com>, linux-staging@lists.linux.dev
Cc: gregkh@linuxfoundation.org, guilherme@puida.xyz,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/8] staging: rtl8723bs: Fix coding style incosistencies in rtw_security.h
Date: Thu, 12 Sep 2024 22:01:51 +0200 [thread overview]
Message-ID: <974c3e9a-c0f6-493a-a865-4f01f41c4087@gmail.com> (raw)
In-Reply-To: <20240912040409.3315067-1-sayyad.abid16@gmail.com>
On 9/12/24 06:04, Sayyad Abid wrote:
> This patch series improves code readability by addressing coding style
> issues in `rtw_security.h`. These changes aim to enhance the
> maintainability and clarity of the codebase by ensuring compliance with
> the Linux kernel's coding standards.
>
> The coding style violations were identified using
> `scripts/checkpatch.pl` on `rtw_security.h`.
>
> ### Changes in v2:
> - Split the original patch into a series of 8 smaller patches, each
> addressing a distinct coding style issue as suggested by Greg's bot.
> - Fixed indentation issues, placement of braces, and removal of spaces
> before tabs.
> - Improved commit messages with detailed explanations for each change.
>
> For reference, here is the `v1` submission:
> https://lore.kernel.org/all/20240911133549.2664372-1-sayyad.abid16@gmail.com/
>
>
> Sayyad Abid (8):
> staging: rtl8723bs: include: Fix open brace position in rtw_security.h
> staging: rtl8723bs: include: Fix indent for switch case in
> rtw_security.h
> staging: rtl8723bs: include: Fix indent for switch block in
> rtw_security.h
> staging: rtl8723bs: include: Fix use of tabs for indent in
> rtw_security.h
> staging: rtl8723bs: include: Fix indent for struct _byte_ in
> rtw_security.h
> staging: rtl8723bs: include: Fix indent for else block struct in
> rtw_security.h
> staging: rtl8723bs: include: Fix trailing */ position in
> rtw_security.h
> staging: rtl8723bs: include: Remove spaces before tabs in
> rtw_security.h
>
> .../staging/rtl8723bs/include/rtw_security.h | 124 +++++++++---------
> 1 file changed, 62 insertions(+), 62 deletions(-)
>
> --
> 2.39.2
>
Tested-by: Philipp Hortmann <philipp.g.hortmann@gmail.com>
prev parent reply other threads:[~2024-09-12 20:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 4:04 Sayyad Abid
2024-09-12 4:04 ` [PATCH v2 1/8] staging: rtl8723bs: include: Fix open brace position " Sayyad Abid
2024-09-12 4:04 ` [PATCH v2 2/8] staging: rtl8723bs: include: Fix indent for switch case " Sayyad Abid
2024-09-12 4:04 ` [PATCH v2 3/8] staging: rtl8723bs: include: Fix indent for switch block " Sayyad Abid
2024-09-12 4:04 ` [PATCH v2 4/8] staging: rtl8723bs: include: Fix use of tabs for indent " Sayyad Abid
2024-09-12 4:04 ` [PATCH v2 5/8] staging: rtl8723bs: include: Fix indent for struct _byte_ " Sayyad Abid
2024-09-12 4:04 ` [PATCH v2 6/8] staging: rtl8723bs: include: Fix indent for else block struct " Sayyad Abid
2024-09-12 4:04 ` [PATCH v2 7/8] staging: rtl8723bs: include: Fix trailing */ position " Sayyad Abid
2024-09-12 4:04 ` [PATCH v2 8/8] staging: rtl8723bs: include: Remove spaces before tabs " Sayyad Abid
2024-09-12 20:01 ` Philipp Hortmann [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=974c3e9a-c0f6-493a-a865-4f01f41c4087@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=guilherme@puida.xyz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=sayyad.abid16@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
all inboxes | Powered by JetHome®