Florian Fainelli wrote: > diff --git a/drivers/leds/Kconfig b/drivers/leds/Kconfig > index 87d2046..fdc5a8a 100644 > --- a/drivers/leds/Kconfig > +++ b/drivers/leds/Kconfig > @@ -128,5 +128,12 @@ config LEDS_TRIGGER_HEARTBEAT > load average. > If unsure, say Y. > > +config LEDS_TRIGGER_NETWORK_ACT > + tristate "LED Network Activity Trigger"
Module isn't possible, you call the led trigger from net/core/dev.c. > diff --git a/net/core/dev.c b/net/core/dev.c > index ee051bb..a3a4115 100644 > --- a/net/core/dev.c > +++ b/net/core/dev.c > @@ -117,6 +117,7 @@ > #include <linux/err.h> > #include <linux/ctype.h> > #include <linux/if_arp.h> > +#include <linux/leds.h> > > /* > * The list of packet types we will receive (as opposed to discard) > @@ -1523,6 +1524,7 @@ gso: > * stops preemption for RCU. > */ > rcu_read_lock_bh(); > + ledtrig_network_activity(); Besides missing a declaration and not linking without the network LED config option, its pretty ridiculous to call this for every packet just to make a led blink. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html