From: Mateusz Kulikowski <mateusz.kulikowski@gmail.com>
To: gregkh@linuxfoundation.org
Cc: Mateusz Kulikowski <mateusz.kulikowski@gmail.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/8] staging: rtl8192e: Fix more checkpatch.pl warnings
Date: Wed, 8 Apr 2015 01:08:49 +0200 [thread overview]
Message-ID: <1428448137-26768-1-git-send-email-mateusz.kulikowski@gmail.com> (raw)
This series of patches fixes another set of checkpatch.pl warnings.
Most of the patches are trivial, with the exception of #8, #7 and #5;
Driver logic should not be affected.
Some of the patches cause LONG_LINE warnings, but fix has to wait until
I do more driver refactorings (It's hard to keep line length when variable
names have 30 characters).
Series should apply to staging-next/testing (c610f7f7).
Smoke tested on rtl8192e card vs staging-next:
- Module load/unload
- Interface up/down
Mateusz Kulikowski (8):
staging: rtl8192e: Fix SPACE_BEFORE_TAB warnings
staging: rtl8192e: Copy comments from r819XE_phyreg.h to r8192E_phyreg.h
staging: rtl8192e: remove r819xE_phyreg.h
staging: rtl8192e: Fix SPACING errors
staging: rtl8192e: Remove bb tx gains from r8192_priv
staging: rtl8192e: Fix LINE_SPACING warning
staging: rtl8192e: Fix DEEP_INDENTATION warnings in rtllib_parse_info_param()
staging: rtl8192e: Fix DEEP_INDENTATION warnings in rtl_dm.c
drivers/staging/rtl8192e/rtl8192e/r8192E_dev.c | 5 +-
drivers/staging/rtl8192e/rtl8192e/r8192E_phy.c | 2 +-
drivers/staging/rtl8192e/rtl8192e/r8192E_phyreg.h | 1496 +++++++++++----------
drivers/staging/rtl8192e/rtl8192e/r819xE_phyreg.h | 908 -------------
drivers/staging/rtl8192e/rtl8192e/rtl_core.c | 6 +-
drivers/staging/rtl8192e/rtl8192e/rtl_core.h | 20 +-
drivers/staging/rtl8192e/rtl8192e/rtl_dm.c | 821 +++--------
drivers/staging/rtl8192e/rtl8192e/rtl_dm.h | 9 +
drivers/staging/rtl8192e/rtllib_debug.h | 3 +-
drivers/staging/rtl8192e/rtllib_rx.c | 23 +-
10 files changed, 1014 insertions(+), 2279 deletions(-)
delete mode 100644 drivers/staging/rtl8192e/rtl8192e/r819xE_phyreg.h
--
1.8.4.1
next reply other threads:[~2015-04-07 23:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 23:08 Mateusz Kulikowski [this message]
2015-04-07 23:08 ` [PATCH 1/8] staging: rtl8192e: Fix SPACE_BEFORE_TAB warnings Mateusz Kulikowski
2015-04-07 23:08 ` [PATCH 2/8] staging: rtl8192e: Copy comments from r819XE_phyreg.h to r8192E_phyreg.h Mateusz Kulikowski
2015-04-07 23:08 ` [PATCH 3/8] staging: rtl8192e: remove r819xE_phyreg.h Mateusz Kulikowski
2015-04-07 23:08 ` [PATCH 4/8] staging: rtl8192e: Fix SPACING errors Mateusz Kulikowski
2015-04-07 23:08 ` [PATCH 5/8] staging: rtl8192e: Remove bb tx gains from r8192_priv Mateusz Kulikowski
2015-04-07 23:08 ` [PATCH 6/8] staging: rtl8192e: Fix LINE_SPACING warning Mateusz Kulikowski
2015-04-07 23:08 ` [PATCH 7/8] staging: rtl8192e: Fix DEEP_INDENTATION warnings in rtllib_parse_info_param() Mateusz Kulikowski
2015-04-07 23:08 ` [PATCH 8/8] staging: rtl8192e: Fix DEEP_INDENTATION warnings in rtl_dm.c Mateusz Kulikowski
2015-04-13 22:37 ` [PATCH 0/8] staging: rtl8192e: Fix more checkpatch.pl warnings Mateusz Kulikowski
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=1428448137-26768-1-git-send-email-mateusz.kulikowski@gmail.com \
--to=mateusz.kulikowski@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/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®