From: Khadija Kamran <kamrankhadijadj@gmail.com>
To: outreachy@lists.linux.dev
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: [PATCH v5 0/4] staging: rtl8192e: code cleanup patches
Date: Sat, 25 Mar 2023 03:31:27 +0500 [thread overview]
Message-ID: <cover.1679696777.git.kamrankhadijadj@gmail.com> (raw)
Fix several cleanup issues reported by checkpatch.pl in module
staging/rtl8192e in file rtllib_rx.c
Changes in v5:
- Resent the correct patchset becuase mistakenly sent a wrong patchset
in the previous revision.
Changes in v4:
- Changed the subject of the cover-letter that was mistakenly edited in
the previous patchset.
Changes in v3:
- Changed the description of all patches in order to explain 'why' the
patches need to be merged.
Changes in v2:
- Resent patchset with the correct email address
Khadija Kamran (4):
staging: rtl8192e: remove extra blank lines
staging: rtl8192e: add blank lines after declarations
staging: rtl8192e: add spaces around binary operators
staging: rtl8192e: remove blank lines after '{'
drivers/staging/rtl8192e/rtllib_rx.c | 73 +++++++++++-----------------
1 file changed, 29 insertions(+), 44 deletions(-)
--
2.34.1
next reply other threads:[~2023-03-24 22:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 22:31 Khadija Kamran [this message]
2023-03-24 22:31 ` [PATCH v5 1/4] staging: rtl8192e: remove extra blank lines Khadija Kamran
2023-03-24 22:31 ` [PATCH v5 2/4] staging: rtl8192e: add blank lines after declarations Khadija Kamran
2023-03-24 22:31 ` [PATCH v5 3/4] staging: rtl8192e: add spaces around binary operators Khadija Kamran
2023-03-24 22:31 ` [PATCH v5 4/4] staging: rtl8192e: remove blank lines after '{' Khadija Kamran
2023-03-24 23:10 ` [PATCH v5 0/4] staging: rtl8192e: code cleanup patches 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.1679696777.git.kamrankhadijadj@gmail.com \
--to=kamrankhadijadj@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@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;
as well as URLs for NNTP newsgroup(s).