Re: [PATCH] leds: trigger: Introduce a NETDEV trigger

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
Subject: Re: [PATCH] leds: trigger: Introduce a NETDEV trigger
From: Andrew Lunn <andrew@xxxxxxx>
Date: Tue, 28 Nov 2017 23:50:51 +0100
Cc: Ben Whitten <ben.whitten@xxxxxxxxx>, rpurdie@xxxxxxxxx, jacek.anaszewski@xxxxxxxxx, pavel@xxxxxx, linux-leds@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxxxxxx
In-reply-to: <f6edbdbb-2b9d-5ee6-7a74-0567ff7d9ded@infradead.org>
References: <1511906058-30649-1-git-send-email-ben.whitten@gmail.com> <1511906058-30649-2-git-send-email-ben.whitten@gmail.com> <f6edbdbb-2b9d-5ee6-7a74-0567ff7d9ded@infradead.org>
User-agent: Mutt/1.5.23 (2014-03-12)

> What LEDs do LED triggers manipulate?  I.e., where are they?

Any LEDs which the LED subsystem controls.

This is emulating what PHYs can do with there LEDs, but using generic
LEDs.

     Andrew

References:
- [PATCH] Introduce a NETDEV LED trigger
  - From: Ben Whitten
- [PATCH] leds: trigger: Introduce a NETDEV trigger
  - From: Ben Whitten
- Re: [PATCH] leds: trigger: Introduce a NETDEV trigger
  - From: Randy Dunlap

Prev by Date: Re: [PATCH] leds: trigger: Introduce a NETDEV trigger
Next by Date: RE: Bug when using both "set" and "blink" functions
Previous by thread: Re: [PATCH] leds: trigger: Introduce a NETDEV trigger
Next by thread: Re: [PATCH] leds: trigger: Introduce a NETDEV trigger
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Security] [Bugtraq] [Linux OMAP] [Linux MIPS] [ECOS] [Asterisk Internet PBX] [Linux API]

Powered by Linux