From: Subrata Modak <tosubrata@gmail.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: Sachin Sant <sachinp@in.ibm.com>,
Subrata Modak <tosubrata@gmail.com>,
netdev <netdev@vger.kernel.org>,
linux-next@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] Re: Next March 25: net/netfilter/xt_LED build failure.
Date: Wed, 25 Mar 2009 19:27:59 +0530 [thread overview]
Message-ID: <20090325135759.4397.53055.sendpatchset@subratamodak.linux.ibm.com> (raw)
Hi David,
>Today's next randconfig build on x86 failed with following error.
>
>net/netfilter/xt_LED.c:40: error: field netfilter_led_trigger has incomplete type
>net/netfilter/xt_LED.c: In function led_timeout_callback:
>net/netfilter/xt_LED.c:78: warning: unused variable ledinternal
>net/netfilter/xt_LED.c: In function led_tg_check:
>net/netfilter/xt_LED.c:102: error: implicit declaration of function led_trigger_register
>net/netfilter/xt_LED.c: In function led_tg_destroy:
>net/netfilter/xt_LED.c:135: error: implicit declaration of function led_trigger_unregister
>
>CONFIG_LED_TRIGGER is not set.
>
>complete .config attached.
The following patch will solve the build problem reported by Sachin.
But would leave the following warnings. I hope we can ignore them:
net/netfilter/xt_LED.c: In function âled_timeout_callbackâ:
net/netfilter/xt_LED.c:78: warning: unused variable âledinternalâ
net/netfilter/xt_LED.c: In function âled_tg_checkâ:
net/netfilter/xt_LED.c:87: warning: unused variable âerrâ
Signed-Off-By: Subrata Modak<subrata@linux.vnet.ibm.com>
---
--- a/linux-2.6.29/include/linux/leds.h 2009-03-25 18:38:07.000000000 +0530
+++ b/linux-2.6.29/include/linux/leds.h 2009-03-25 18:24:55.000000000 +0530
@@ -73,9 +73,6 @@ extern void led_classdev_resume(struct l
/*
* LED Triggers
*/
-#ifdef CONFIG_LEDS_TRIGGERS
-
-#define TRIG_NAME_MAX 50
struct led_trigger {
/* Trigger Properties */
@@ -91,6 +88,10 @@ struct led_trigger {
struct list_head next_trig;
};
+#ifdef CONFIG_LEDS_TRIGGERS
+
+#define TRIG_NAME_MAX 50
+
/* Registration functions for complex triggers */
extern int led_trigger_register(struct led_trigger *trigger);
extern void led_trigger_unregister(struct led_trigger *trigger);
--- a/linux-2.6.29/net/netfilter/xt_LED.c 2009-03-25 18:38:08.000000000 +0530
+++ b/linux-2.6.29/net/netfilter/xt_LED.c 2009-03-25 18:26:55.000000000 +0530
@@ -99,6 +99,7 @@ static bool led_tg_check(const struct xt
ledinternal->netfilter_led_trigger.name = ledinfo->id;
+#ifdef CONFIG_LEDS_TRIGGERS
err = led_trigger_register(&ledinternal->netfilter_led_trigger);
if (err) {
printk(KERN_CRIT KBUILD_MODNAME
@@ -108,7 +109,7 @@ static bool led_tg_check(const struct xt
": Trigger name is already in use.\n");
goto exit_alloc;
}
-
+#endif
/* See if we need to set up a timer */
if (ledinfo->delay > 0)
setup_timer(&ledinternal->timer, led_timeout_callback,
@@ -118,8 +119,10 @@ static bool led_tg_check(const struct xt
return true;
+#ifdef CONFIG_LEDS_TRIGGERS
exit_alloc:
kfree(ledinternal);
+#endif
return false;
}
@@ -132,7 +135,9 @@ static void led_tg_destroy(const struct
if (ledinfo->delay > 0)
del_timer_sync(&ledinternal->timer);
+#ifdef CONFIG_LEDS_TRIGGERS
led_trigger_unregister(&ledinternal->netfilter_led_trigger);
+#endif
kfree(ledinternal);
}
--
Regards--
Subrata
next reply other threads:[~2009-03-25 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 13:57 Subrata Modak [this message]
2009-03-25 14:08 ` [PATCH] Re: Next March 25: net/netfilter/xt_LED build failure Patrick McHardy
-- strict thread matches above, loose matches on Subject: below --
2009-03-25 14:31 Subrata Modak
2009-03-25 14:34 ` Patrick McHardy
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=20090325135759.4397.53055.sendpatchset@subratamodak.linux.ibm.com \
--to=tosubrata@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sachinp@in.ibm.com \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).