From: Srishti Sharma <srishtishar@gmail.com>
To: gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
outreachy-kernel@googlegroups.com,
Srishti Sharma <srishtishar@gmail.com>
Subject: [PATCH 0/4] Code cleanup
Date: Thu, 19 Oct 2017 01:00:25 +0530 [thread overview]
Message-ID: <cover.1508354332.git.srishtishar@gmail.com> (raw)
This patch series performs code cleanup like using list_for_each_entry_safe
to make code more compact and using list_entry instead of container_of for
struct list_head* variable types.
Srishti Sharma (4):
Staging: rtl8188eu: core: rtw_xmit: Use list_for_each_entry_safe
Staging: rtl8188eu: core: rtw_ap: Use list_for_each_entry_safe
Staging: rtl8188eu: core: rtw_mlme_ext: Use list_for_each_entry_safe
Staging: rtl8188eu: core: Use list_entry instead of container_of
drivers/staging/rtl8188eu/core/rtw_ap.c | 38 ++++++++-------------------
drivers/staging/rtl8188eu/core/rtw_mlme.c | 8 +++---
drivers/staging/rtl8188eu/core/rtw_mlme_ext.c | 11 ++++----
drivers/staging/rtl8188eu/core/rtw_sta_mgt.c | 12 ++++-----
drivers/staging/rtl8188eu/core/rtw_xmit.c | 30 +++++++--------------
5 files changed, 36 insertions(+), 63 deletions(-)
--
2.7.4
next reply other threads:[~2017-10-18 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 19:30 Srishti Sharma [this message]
2017-10-18 19:30 ` [PATCH 1/4] Staging: rtl8188eu: core: rtw_xmit: Use list_for_each_entry_safe Srishti Sharma
2017-10-18 19:31 ` [PATCH 2/4] Staging: rtl8188eu: core: rtw_ap: " Srishti Sharma
2017-10-19 8:17 ` Dan Carpenter
2017-10-18 19:31 ` [PATCH 3/4] Staging: rtl8188eu: core: rtw_mlme_ext: " Srishti Sharma
2017-10-19 8:14 ` Dan Carpenter
2017-10-18 19:32 ` [PATCH 4/4] Staging: rtl8188eu: core: Use list_entry instead of container_of Srishti Sharma
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.1508354332.git.srishtishar@gmail.com \
--to=srishtishar@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome