From: navin patidar <navin.patidar@gmail.com>
To: gregkh@linuxfoundation.org
Cc: Larry.Finger@lwfinger.net, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org,
navin patidar <navin.patidar@gmail.com>
Subject: [PATCH 05/13] staging: rtl8188eu: Remove unused struct intf_priv
Date: Fri, 6 Jun 2014 21:45:13 +0530 [thread overview]
Message-ID: <1402071320-14400-4-git-send-email-navin.patidar@gmail.com> (raw)
In-Reply-To: <1402071320-14400-1-git-send-email-navin.patidar@gmail.com>
Signed-off-by: navin patidar <navin.patidar@gmail.com>
---
drivers/staging/rtl8188eu/include/osdep_intf.h | 33 ------------------------
1 file changed, 33 deletions(-)
diff --git a/drivers/staging/rtl8188eu/include/osdep_intf.h b/drivers/staging/rtl8188eu/include/osdep_intf.h
index a5b3bd3..523141a 100644
--- a/drivers/staging/rtl8188eu/include/osdep_intf.h
+++ b/drivers/staging/rtl8188eu/include/osdep_intf.h
@@ -24,39 +24,6 @@
#include <osdep_service.h>
#include <drv_types.h>
-struct intf_priv {
- u8 *intf_dev;
- u32 max_iosz; /* USB2.0: 128, USB1.1: 64, SDIO:64 */
- u32 max_xmitsz; /* USB2.0: unlimited, SDIO:512 */
- u32 max_recvsz; /* USB2.0: unlimited, SDIO:512 */
-
- u8 *io_rwmem;
- u8 *allocated_io_rwmem;
- u32 io_wsz; /* unit: 4bytes */
- u32 io_rsz;/* unit: 4bytes */
- u8 intf_status;
-
- void (*_bus_io)(u8 *priv);
-
-/*
-Under Sync. IRP (SDIO/USB)
-A protection mechanism is necessary for the io_rwmem(read/write protocol)
-
-Under Async. IRP (SDIO/USB)
-The protection mechanism is through the pending queue.
-*/
- struct mutex ioctl_mutex;
- /* when in USB, IO is through interrupt in/out endpoints */
- struct usb_device *udev;
- struct urb *piorw_urb;
- u8 io_irp_cnt;
- u8 bio_irp_pending;
- struct semaphore io_retevt;
- struct timer_list io_timer;
- u8 bio_irp_timeout;
- u8 bio_timer_cancel;
-};
-
u8 rtw_init_drv_sw(struct adapter *padapter);
u8 rtw_free_drv_sw(struct adapter *padapter);
u8 rtw_reset_drv_sw(struct adapter *padapter);
--
1.7.10.4
next prev parent reply other threads:[~2014-06-06 16:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 16:15 [PATCH 02/13] staging: rtl8188eu: Remove rtw_deinit_intf_priv() navin patidar
2014-06-06 16:15 ` [PATCH 03/13] staging: rtl8188eu: Remove rtw_init_intf_priv() navin patidar
2014-06-06 16:15 ` [PATCH 04/13] staging: rtl8188eu:Move rtw_hw_[suspend,resume]() to rtw_pwrctrl.c navin patidar
2014-06-06 16:15 ` navin patidar [this message]
2014-06-06 16:15 ` [PATCH 06/13] staging: rtl8188eu: Remove unused funtion _rtw_read_mem() navin patidar
2014-06-10 7:28 ` Dan Carpenter
2014-06-11 4:13 ` navin patidar
2014-06-06 16:15 ` [PATCH 07/13] staging: rtl8188eu: Remove unused function _rtw_write_mem() navin patidar
2014-06-06 16:15 ` [PATCH 08/13] staging: rtl8188eu: Remove unused function declaration and macro navin patidar
2014-06-06 16:15 ` [PATCH 09/13] staging: rtl8188eu: rtw_io.h: Remove unused structures navin patidar
2014-06-06 16:15 ` [PATCH 10/13] staging: rtl8188eu: HalPhyRf_8188e.c: Remove unused macro navin patidar
2014-06-06 16:15 ` [PATCH 11/13] staging: rtl8188eu: HalPhyRf_8188e.c: Remove unnecessary comments navin patidar
2014-06-06 16:15 ` [PATCH] staging: rtl8188eu: os_dep: usb_intf.c: Cleaning up unnecessary code navin patidar
2014-06-06 16:47 ` 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=1402071320-14400-4-git-send-email-navin.patidar@gmail.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