From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Greg Kroah-Hartman <gregkh@suse.de>,
Anthony Wong <awong1@novell.com>,
Staging <devel@driverdev.osuosl.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] STAGING: Remove dead code rtl8192e, ieee80211_crypt_wep.c
Date: Tue, 22 Sep 2009 20:34:24 +0530 [thread overview]
Message-ID: <1253631864.3784.38.camel@ht.satnam> (raw)
Remove dead code from drivers/staging/rtl8192e/ieee80211/ieee80211_crypt_wep.c
This also fixed following 'make includecheck' warnings:
drivers/staging/rtl8192e/ieee80211/ieee80211_crypt_wep.c: rtl_crypto.h is included more than once.
drivers/staging/rtl8192e/ieee80211/ieee80211_crypt_wep.c: linux/crypto.h is included more than once.
drivers/staging/rtl8192e/ieee80211/ieee80211_crypt_wep.c: asm/scatterlist.h is included more than once.
drivers/staging/rtl8192e/ieee80211/ieee80211_crypt_wep.c: linux/crc32.h is included more than once.
Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
---
.../rtl8192e/ieee80211/ieee80211_crypt_wep.c | 17 -----------------
1 files changed, 0 insertions(+), 17 deletions(-)
diff --git a/drivers/staging/rtl8192e/ieee80211/ieee80211_crypt_wep.c b/drivers/staging/rtl8192e/ieee80211/ieee80211_crypt_wep.c
index 5678313..5289c27 100644
--- a/drivers/staging/rtl8192e/ieee80211/ieee80211_crypt_wep.c
+++ b/drivers/staging/rtl8192e/ieee80211/ieee80211_crypt_wep.c
@@ -9,7 +9,6 @@
* more details.
*/
-//#include <linux/config.h>
#include <linux/version.h>
#include <linux/module.h>
#include <linux/init.h>
@@ -32,19 +31,8 @@
#else
#include <linux/scatterlist.h>
#endif
-//#include <asm/scatterlist.h>
#include <linux/crc32.h>
-//
-/*
-#if (LINUX_VERSION_CODE < KERNEL_VERSION(2,5,0))
-#include "rtl_crypto.h"
-#else
-#include <linux/crypto.h>
-#endif
-#include <asm/scatterlist.h>
-#include <linux/crc32.h>
-*/
MODULE_AUTHOR("Jouni Malinen");
MODULE_DESCRIPTION("Host AP crypt: WEP");
MODULE_LICENSE("GPL");
@@ -380,14 +368,9 @@ void __exit ieee80211_crypto_wep_exit(void)
void ieee80211_wep_null(void)
{
-// printk("============>%s()\n", __FUNCTION__);
return;
}
#if (LINUX_VERSION_CODE > KERNEL_VERSION(2,5,0))
-//EXPORT_SYMBOL(ieee80211_wep_null);
#else
EXPORT_SYMBOL_NOVERS(ieee80211_wep_null);
#endif
-
-//module_init(ieee80211_crypto_wep_init);
-//module_exit(ieee80211_crypto_wep_exit);
--
1.6.0.6
reply other threads:[~2009-09-22 15:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1253631864.3784.38.camel@ht.satnam \
--to=jaswinder@kernel.org \
--cc=awong1@novell.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--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