[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210727165605.5c8ddb68@thinkpad>
Date: Tue, 27 Jul 2021 16:56:05 +0200
From: Marek BehĂșn <kabel@...nel.org>
To: Michael Walle <michael@...le.cc>
Cc: andrew@...n.ch, anthony.l.nguyen@...el.com, bigeasy@...utronix.de,
davem@...emloft.net, dvorax.fuxbrumer@...ux.intel.com,
f.fainelli@...il.com, hkallweit1@...il.com,
jacek.anaszewski@...il.com, kuba@...nel.org, kurt@...utronix.de,
linux-leds@...r.kernel.org, netdev@...r.kernel.org, pavel@....cz,
sasha.neftin@...el.com, vinicius.gomes@...el.com,
vitaly.lifshits@...el.com
Subject: Re: [PATCH net-next 5/5] igc: Export LEDs
Hi Michael,
On Tue, 27 Jul 2021 10:15:28 +0200
Michael Walle <michael@...le.cc> wrote:
> Why do we have to distiguish between LEDs connected to the PHY and LEDs
> connected to the MAC at all? Why not just name it ethN either if its behind
> the PHY or the MAC? Does it really matter from the users POV?
Because
1. network interfaces can be renamed
2. network interfaces can be moved between network namespaces. The LED
subsystem is agnostic to network namespaces
So it can for example happen that within a network namespace you
have only one interface, eth0, but in /sys/class/leds you would see
eth0:green:activity
eth1:green:activity
So you would know that there are at least 2 network interfaces on the
system, and also with renaming it can happen that the first LED is not
in fact connected to the eth0 interface in your network namespace.
Marek
Powered by blists - more mailing lists