From: R Veera Kumar <vkor@vkten.in>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: R Veera Kumar <vkor@vkten.in>,
outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: [PATCH v3 0/3] staging: rtl8723bs: os_dep: Remove commented code lines, correct longline comments, remove whitespace in code
Date: Sat, 21 Mar 2020 10:08:56 +0530 [thread overview]
Message-ID: <cover.1584764104.git.vkor@vkten.in> (raw)
Patch 1:
Remove multiple commented out code lines.
Remove blank lines next to them.
Patch 2:
Correct long line comments to match coding style of
respecting 80 character per line limit.
Patch 3:
Remove four leading whitespace characters in code line.
Please apply the patches in series.
Changes since V2:
- Remove commented code lines
- Drop a code line with correct leading whitespace
Changes since V1:
- Missed staging: rtl8723bs: os_dep: in cover letter
---
R Veera Kumar (3):
staging: rtl8723bs: os_dep: Remove commented out code lines
staging: rtl8723bs: os_dep: Correct long line comments
staging: rtl8723bs: os_dep: Remove whitespace characters in code line
drivers/staging/rtl8723bs/os_dep/recv_linux.c | 30 ++++++++-----------
1 file changed, 12 insertions(+), 18 deletions(-)
--
2.20.1
next reply other threads:[~2020-03-21 4:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 4:38 R Veera Kumar [this message]
2020-03-21 4:38 ` [PATCH v3 1/3] staging: rtl8723bs: os_dep: Remove commented out code lines R Veera Kumar
2020-03-21 7:32 ` [Outreachy kernel] " Julia Lawall
2020-03-21 8:07 ` R Veera Kumar
2020-03-21 8:46 ` Julia Lawall
2020-03-21 9:10 ` R Veera Kumar
2020-03-21 9:11 ` Julia Lawall
2020-03-21 4:38 ` [PATCH v3 2/3] staging: rtl8723bs: os_dep: Correct long line comments R Veera Kumar
2020-03-21 4:38 ` [PATCH v3 3/3] staging: rtl8723bs: os_dep: Remove whitespace characters in code line R Veera 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.1584764104.git.vkor@vkten.in \
--to=vkor@vkten.in \
--cc=gregkh@linuxfoundation.org \
--cc=outreachy-kernel@googlegroups.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.