From: Navya Sri Nizamkari <navyasri.tech@gmail.com>
To: outreachy-kernel@googlegroups.com
Subject: [PATCH v4 0/4] staging: rtl8192u: Fix warnings in ieee80211_crypt.c
Date: Thu, 26 Feb 2015 12:38:13 +0530 [thread overview]
Message-ID: <cover.1424934230.git.navyasri.tech@gmail.com> (raw)
[changes in v4]
In v4 version, code indentation is changed to look better.
[changes in v3]
In v3 version, the printk functions which are changed to pr_dbg
are changed to pr_debug as pr_dbg gives a 'implicit declaration of
function' warning when you build.
[changes in v2]
In v2 version of this patchset I correct the commit message of
[PATCH 1/4] to be clearer and remove a comment from [PATCH 2/4]
whose style was changed in version v1.
[original cover letter]
This patchset removes an unnecessary comment and clears checkpatch.pl
warnings in ieee80211_crypt.c such as:
convert printk to a preferable function like netdev_dbg or pr_dbg,
replace asm header files with
linux ones, fix the quoted string split across a line.
Navya Sri Nizamkari (4):
staging: rtl8192u: Convert from printk into netdev_dbg or pr_dbg
staging: rtl8192u: Remove unnecessary comment.
staging: rtl8192u: Replace asm header files with linux ones.
staging: rtl8192u: Fix quoted string split across lines.
.../staging/rtl8192u/ieee80211/ieee80211_crypt.c | 21 ++++++++++-----------
1 file changed, 10 insertions(+), 11 deletions(-)
--
1.9.1
next reply other threads:[~2015-02-26 7:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 7:08 Navya Sri Nizamkari [this message]
2015-02-26 7:13 ` [PATCH v4 1/4] staging: rtl8192u: Convert from printk into netdev_dbg or pr_debug Navya Sri Nizamkari
2015-02-26 21:47 ` [Outreachy kernel] " Greg KH
2015-02-26 7:19 ` [PATCH v4 2/4] staging: rtl8192u: Remove unnecessary comment Navya Sri Nizamkari
2015-02-26 7:21 ` [PATCH v4 3/4] staging: rtl8192u: Replace asm header files with linux ones Navya Sri Nizamkari
2015-02-26 7:24 ` [PATCH v4 4/4] staging: rtl8192u: Fix quoted string split across lines Navya Sri Nizamkari
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.1424934230.git.navyasri.tech@gmail.com \
--to=navyasri.tech@gmail.com \
--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.