From: Kushal Kothari <kushalkothari285@gmail.com>
To: gregkh@linuxfoundation.org
Cc: fabioaiuto83@gmail.com, kushalkothari285@gmail.com,
ross.schm.dev@gmail.com, fmdefrancesco@gmail.com,
marcocesati@gmail.com, straube.linux@gmail.com,
philippesdixon@gmail.com, manuelpalenzuelamerino@gmail.com,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
mike.rapoport@gmail.com, kushalkotharitest@googlegroups.com,
outreachy-kernel@googlegroups.com
Subject: [PATCH 0/4] staging: rtl8723bs: core: Cleanup patchset for style issues in rtw_cmd.c
Date: Fri, 22 Oct 2021 01:27:49 +0530 [thread overview]
Message-ID: <cover.1634845504.git.kushalkothari285@gmail.com> (raw)
These patches make changes to clean up style issues identified
by checkpatch.
Kushal Kothari (4):
staging: rtl8723bs: core: Remove true and false comparison
staging: rtl8723bs: core: Remove unnecessary parentheses
staging: rtl8723bs: core: Remove unnecessary space after a cast
staging: rtl8723bs: core: Remove unnecessary blank lines
drivers/staging/rtl8723bs/core/rtw_cmd.c | 75 +++++++++++-------------
1 file changed, 35 insertions(+), 40 deletions(-)
--
2.25.1
next reply other threads:[~2021-10-21 19:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 19:57 Kushal Kothari [this message]
2021-10-21 19:57 ` [PATCH 1/4] staging: rtl8723bs: core: Remove true and false comparison Kushal Kothari
2021-10-22 2:44 ` [Outreachy kernel] " Praveen Kumar
2021-11-03 11:52 ` Dan Carpenter
2021-10-21 19:57 ` [PATCH 2/4] staging: rtl8723bs: core: Remove unnecessary parentheses Kushal Kothari
2021-10-21 19:57 ` [PATCH 3/4] staging: rtl8723bs: core: Remove unnecessary space after a cast Kushal Kothari
2021-10-22 2:48 ` [Outreachy kernel] " Praveen Kumar
2021-10-21 19:57 ` [PATCH 4/4] staging: rtl8723bs: core: Remove unnecessary blank lines Kushal Kothari
2021-10-22 6:03 ` Greg KH
2021-10-22 2:45 ` [Outreachy kernel] [PATCH 0/4] staging: rtl8723bs: core: Cleanup patchset for style issues in rtw_cmd.c Praveen Kumar
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=cover.1634845504.git.kushalkothari285@gmail.com \
--to=kushalkothari285@gmail.com \
--cc=fabioaiuto83@gmail.com \
--cc=fmdefrancesco@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kushalkotharitest@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=manuelpalenzuelamerino@gmail.com \
--cc=marcocesati@gmail.com \
--cc=mike.rapoport@gmail.com \
--cc=outreachy-kernel@googlegroups.com \
--cc=philippesdixon@gmail.com \
--cc=ross.schm.dev@gmail.com \
--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.