linux-kernel - [PATCH] : Fix unused variable compilation warnings in drivers/net/wan/syncppp.c

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]

Message-ID: <ea11fea30810270548y11453b8i10eb53caff1838e8@mail.gmail.com>
Date:	Mon, 27 Oct 2008 18:18:42 +0530
From:	"Manish Katiyar" <mkatiyar@...il.com>
To:	kernel-janitors@...r.kernel.org, linux-netdev@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>
Cc:	mkatiyar@...il.com
Subject: [PATCH] : Fix unused variable compilation warnings in drivers/net/wan/syncppp.c

Below patch fixes the unused compilation warnings in
drivers/net/wan/syncppp.c when CONFIG_INET is not defined.

Signed-off-by: Manish Katiyar <mkatiyar@...il.com>
---
 drivers/net/wan/syncppp.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/net/wan/syncppp.c b/drivers/net/wan/syncppp.c
index 327d585..11124f3 100644
--- a/drivers/net/wan/syncppp.c
+++ b/drivers/net/wan/syncppp.c
@@ -756,10 +756,10 @@ static void sppp_cisco_input (struct sppp *sp,
struct sk_buff *skb)
 	case CISCO_ADDR_REQ:
 		/* Stolen from net/ipv4/devinet.c -- SIOCGIFADDR ioctl */
 		{
-		struct in_device *in_dev;
-		struct in_ifaddr *ifa;
 		__be32 addr = 0, mask = htonl(~0U); /* FIXME: is the mask correct? */
 #ifdef CONFIG_INET
+		struct in_device *in_dev;
+		struct in_ifaddr *ifa;
 		rcu_read_lock();
 		if ((in_dev = __in_dev_get_rcu(dev)) != NULL)
 		{
-- 
1.5.4.3


Thanks -
Manish
--
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/