This is a note to let you know that I've just added the patch titled
ifenslave: Fix unused variable warnings.
to the 3.0-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
ifenslave-fix-unused-variable-warnings.patch
and it can be found in the queue-3.0 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.
>From 450faacc621dbe0a4945ed8292afd45f4602d263 Mon Sep 17 00:00:00 2001
From: "David S. Miller" <[email protected]>
Date: Sat, 26 Nov 2011 16:54:17 -0500
Subject: ifenslave: Fix unused variable warnings.
From: "David S. Miller" <[email protected]>
commit 450faacc621dbe0a4945ed8292afd45f4602d263 upstream.
Documentation/networking/ifenslave.c: In function âif_getconfigâ:
Documentation/networking/ifenslave.c:508:14: warning: variable âmtuâ set
but not used [-Wunused-but-set-variable]
Documentation/networking/ifenslave.c:508:6: warning: variable âmetricâ set
but not used [-Wunused-but-set-variable]
The purpose of this function is to simply print out the values
it probes, so...
Signed-off-by: David S. Miller <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
Documentation/networking/ifenslave.c | 2 ++
1 file changed, 2 insertions(+)
--- a/Documentation/networking/ifenslave.c
+++ b/Documentation/networking/ifenslave.c
@@ -539,12 +539,14 @@ static int if_getconfig(char *ifname)
metric = 0;
} else
metric = ifr.ifr_metric;
+ printf("The result of SIOCGIFMETRIC is %d\n", metric);
strcpy(ifr.ifr_name, ifname);
if (ioctl(skfd, SIOCGIFMTU, &ifr) < 0)
mtu = 0;
else
mtu = ifr.ifr_mtu;
+ printf("The result of SIOCGIFMTU is %d\n", mtu);
strcpy(ifr.ifr_name, ifname);
if (ioctl(skfd, SIOCGIFDSTADDR, &ifr) < 0) {
Patches currently in stable-queue which might be from [email protected] are
queue-3.0/ifenslave-fix-unused-variable-warnings.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
