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 v2 0/5] staging: rtl8192e: fix checkpatch issues in rtllib_crypt_ccmp.c
Date: Sun, 2 Apr 2023 19:32:41 +0500 [thread overview]
Message-ID: <cover.1680445545.git.kamrankhadijadj@gmail.com> (raw)
Fix several issues reported by checkpatch in rtllib_crypt_ccmp.c file.
Changes in v2:
- Update variable_name in PATCH 3, 4 and 5 to dot11rsna_{variable_name}
- Remove comment from PATCH 3
Khadija Kamran (5):
staging: rtl8192e: remove extra blank lines in rtllib_crypt_ccmp.c
staging: rtl8192e: fix alignment to match open parenthesis
staging: rtl8192e: avoid CamelCase <dot11RSNAStatsCCMPFormatErrors>
staging: rtl8192e: avoid CamelCase <dot11RSNAStatsCCMPReplays>
staging: rtl8192e: avoid CamelCase <dot11RSNAStatsCCMPDecryptErrors>
drivers/staging/rtl8192e/rtllib_crypt_ccmp.c | 32 +++++++-------------
1 file changed, 11 insertions(+), 21 deletions(-)
--
2.34.1
next reply other threads:[~2023-04-02 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 14:32 Khadija Kamran [this message]
2023-04-02 14:32 ` [PATCH v2 1/5] staging: rtl8192e: remove extra blank lines in rtllib_crypt_ccmp.c Khadija Kamran
2023-04-02 14:32 ` [PATCH v2 2/5] staging: rtl8192e: fix alignment to match open parenthesis Khadija Kamran
2023-04-02 14:32 ` [PATCH v2 3/5] staging: rtl8192e: avoid CamelCase <dot11RSNAStatsCCMPFormatErrors> Khadija Kamran
2023-04-02 14:32 ` [PATCH v2 4/5] staging: rtl8192e: avoid CamelCase <dot11RSNAStatsCCMPReplays> Khadija Kamran
2023-04-02 14:32 ` [PATCH v2 5/5] staging: rtl8192e: avoid CamelCase <dot11RSNAStatsCCMPDecryptErrors> Khadija Kamran
2023-04-02 16:00 ` [PATCH v2 0/5] staging: rtl8192e: fix checkpatch issues in rtllib_crypt_ccmp.c 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.1680445545.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 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.