From: navin.patidar@gmail.com
To: gregkh@linuxfoundation.org, Larry.Finger@lwfinger.net
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
navin patidar <navin.patidar@gmail.com>
Subject: [PATCH 00/13]staging: rtl8188eu: Remove unused functions and variables
Date: Wed, 7 May 2014 09:27:23 +0530 [thread overview]
Message-ID: <5369af4d.8482440a.284c.1d3c@mx.google.com> (raw)
From: navin patidar <navin.patidar@gmail.com>
Following patches remove unused functions, variables and functions with empty
definition.
navin patidar (13):
staging: rtl8188eu: Remove 'semaphore allrxreturnevt' from struct
recv_priv
staging: rtl8188eu: Remove unused member variables of struct
recv_priv
staging: rtl8188eu: Remove 'spinlock_t lock' from struct recv_priv
staging: rtl8188eu: Remove struct zero_bulkout_context
staging: rtl8188eu: Remove function rtw_os_recv_resource_init()
staging: rtl8188eu: Remove function rtw_os_recv_resource_free()
staging: rtl8188eu: Remove function rtw_hostapd_mlme_rx()
staging: rtl8188eu: Remove function rtw_os_recvbuf_resource_free()
staging: rtl8188eu: Remove unused inline function recvframe_push()
staging: rtl8188eu: Remove unused inline function get_rx_status()
staging: rtl8188eu: Remove 'void *precvbuf' from struct recv_frame
staging: rtl8188eu: Remove 'int frame_tag' from struct recv_frame
staging: rtl8188eu: Remove 'u8 fragcnt' from struct recv_frame
drivers/staging/rtl8188eu/core/rtw_mlme_ext.c | 2 --
drivers/staging/rtl8188eu/core/rtw_recv.c | 8 -----
drivers/staging/rtl8188eu/hal/rtl8188eu_recv.c | 2 +-
drivers/staging/rtl8188eu/hal/usb_ops_linux.c | 1 -
drivers/staging/rtl8188eu/include/recv_osdep.h | 4 ---
drivers/staging/rtl8188eu/include/rtw_recv.h | 36 ----------------------
drivers/staging/rtl8188eu/os_dep/recv_linux.c | 25 ---------------
drivers/staging/rtl8188eu/os_dep/usb_ops_linux.c | 7 -----
8 files changed, 1 insertion(+), 84 deletions(-)
--
1.7.10.4
next reply other threads:[~2014-05-07 3:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 3:57 navin.patidar [this message]
2014-05-21 4:10 ` navin patidar
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=5369af4d.8482440a.284c.1d3c@mx.google.com \
--to=navin.patidar@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--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
Powered by JetHome