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/3] staging: rtl8192u: clean up comments in r8192U_dm.c
Date: Sun, 26 Mar 2023 17:18:24 +0500 [thread overview]
Message-ID: <cover.1679831899.git.kamrankhadijadj@gmail.com> (raw)
Clean up several comments in file r8192U_dm.c
Changes in v2:
- Remove the 'commented code' and 'revision history' before
reformatting the block comments, as suggested by Greg. There is no use
in fixing comments, only to remove them in the next commits
- Patch 1: Changed the description and removed extra blank lines under
the change history
- Patch 2: Changed the subject and description
Reviewer feedback on an initial patch suggested additional cleanup
comments. Link to the first patch:
https://lore.kernel.org/outreachy/ZB2a5zwYpBZ%2F6qwU@khadija-virtual-machine/
Khadija Kamran (3):
staging: rtl8192u: remove change history from comments
staging: rtl8192u: remove commented out code
staging: rtl8192u: reformat block comments
drivers/staging/rtl8192u/r8192U_dm.c | 206 +++------------------------
1 file changed, 23 insertions(+), 183 deletions(-)
--
2.34.1
next reply other threads:[~2023-03-26 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 12:18 Khadija Kamran [this message]
2023-03-26 12:18 ` [PATCH v2 1/3] staging: rtl8192u: remove change history from comments Khadija Kamran
2023-03-26 12:18 ` [PATCH v2 2/3] staging: rtl8192u: remove commented out code Khadija Kamran
2023-03-26 12:18 ` [PATCH v2 3/3] staging: rtl8192u: reformat block comments Khadija Kamran
2023-03-27 5:03 ` Dan Carpenter
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.1679831899.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).