linux-kernel - [PATCH] staging: bcm: fix sparse warning in module

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Wed,  1 Oct 2014 22:26:01 +0530
From:	Rahul Bedarkar <rahulbedarkar89@...il.com>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	Matthias Beyer <mail@...ermatthias.de>,
	Jade Bilkey <herself@...fumon.com>,
	Lisa Nguyen <lisa@...apiadmin.com>,
	Dan Carpenter <dan.carpenter@...cle.com>,
	Himangi Saraogi <himangi774@...il.com>,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
	Rahul Bedarkar <rahulbedarkar89@...il.com>
Subject: [PATCH] staging: bcm: fix sparse warning in module_param

This patch fixes sparse warning in module_param
warning: pointer targets in return differ in signedness [-Wpointer-sign]

Signed-off-by: Rahul Bedarkar <rahulbedarkar89@...il.com>
---
 drivers/staging/bcm/InterfaceInit.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/bcm/InterfaceInit.c b/drivers/staging/bcm/InterfaceInit.c
index bb61d34..9eaffd8 100644
--- a/drivers/staging/bcm/InterfaceInit.c
+++ b/drivers/staging/bcm/InterfaceInit.c
@@ -15,7 +15,7 @@ static struct usb_device_id InterfaceUsbtable[] = {
 MODULE_DEVICE_TABLE(usb, InterfaceUsbtable);
 
 static int debug = -1;
-module_param(debug, uint, 0600);
+module_param(debug, int, 0600);
 MODULE_PARM_DESC(debug, "Debug level (0=none,...,16=all)");
 
 static const u32 default_msg =
-- 
1.8.3.2

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/