[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f6edbdbb-2b9d-5ee6-7a74-0567ff7d9ded@infradead.org>
Date: Tue, 28 Nov 2017 14:41:11 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: Ben Whitten <ben.whitten@...il.com>, rpurdie@...ys.net,
jacek.anaszewski@...il.com, pavel@....cz
Cc: linux-leds@...r.kernel.org, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCH] leds: trigger: Introduce a NETDEV trigger
On 11/28/2017 01:54 PM, Ben Whitten wrote:
> diff --git a/drivers/leds/trigger/Kconfig b/drivers/leds/trigger/Kconfig
> index 3f9ddb9..4ec1853 100644
> --- a/drivers/leds/trigger/Kconfig
> +++ b/drivers/leds/trigger/Kconfig
> @@ -126,4 +126,11 @@ config LEDS_TRIGGER_PANIC
> a different trigger.
> If unsure, say Y.
>
> +config LEDS_TRIGGER_NETDEV
> + tristate "LED Netdev Trigger"
> + depends on NET && LEDS_TRIGGERS
> + help
> + This allows LEDs to be controlled by network device activity.
> + If unsure, say Y.
> +
> endif # LEDS_TRIGGERS
What LEDs do LED triggers manipulate? I.e., where are they?
--
~confuzed
Powered by blists - more mailing lists