From: Aaron Lawrence <t4rmin@zohomail.com>
To: gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] staging: rtl8192e: rtllib_tx: code cleanup patches on the rtllib_tx.c file
Date: Mon, 24 Oct 2022 19:25:02 +0700 [thread overview]
Message-ID: <cover.1666612946.git.t4rmin@zohomail.com> (raw)
Multiple patches regarding the cleanup of code in the rtllib_tx.c file.
Fixes were applied according to the report generated by the checkpatch
script on said file, aside from the CamelCase issues.
Aaron Lawrence (5):
Staging: rtl8192e: rtllib_tx: fixed multiple blank lines
Staging: rtl8192e: rtllib_tx: fixed alignment matching open
parenthesis
Staging: rtl8192e: rtllib_tx: added spaces around operators
Staging: rtl8192e: rtllib_tx: fixed lines ending with an open
parenthesis
Staging: rtl8192e: rtllib_tx: removed unnecessary blank line before a
close brace
drivers/staging/rtl8192e/rtllib_tx.c | 42 ++++++++++++----------------
1 file changed, 18 insertions(+), 24 deletions(-)
--
2.38.1
next reply other threads:[~2022-10-25 1:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 12:25 Aaron Lawrence [this message]
2022-10-24 12:26 ` [PATCH 1/5] Staging: rtl8192e: rtllib_tx: fixed multiple blank lines Aaron Lawrence
2022-10-24 12:26 ` [PATCH 2/5] Staging: rtl8192e: rtllib_tx: fixed alignment matching open parenthesis Aaron Lawrence
2022-10-24 12:27 ` [PATCH 3/5] Staging: rtl8192e: rtllib_tx: added spaces around operators Aaron Lawrence
2022-10-24 12:29 ` [PATCH 4/5] Staging: rtl8192e: rtllib_tx: fixed lines ending with an open parenthesis Aaron Lawrence
2022-10-24 12:30 ` [PATCH 5/5] Staging: rtl8192e: rtllib_tx: removed unnecessary blank line before a close brace Aaron Lawrence
2022-10-25 17:21 ` [PATCH 0/5] staging: rtl8192e: rtllib_tx: code cleanup patches on the rtllib_tx.c file Philipp Hortmann
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.1666612946.git.t4rmin@zohomail.com \
--to=t4rmin@zohomail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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®