[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YQAlPrF2uu3Gr+0d@lunn.ch>
Date: Tue, 27 Jul 2021 17:24:46 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Michael Walle <michael@...le.cc>
Cc: Marek BehĂșn <kabel@...nel.org>,
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
> I wasn't talking about ethN being same as the network interface name.
> For clarity I'll use ethernetN now. My question was why would you
> use ethmacN or ethphyN instead if just ethernetN for both. What is
> the reason for having two different names?
We can get into the situation where both the MAC and the PHY have LED
controllers. So we need to ensure the infrastructure we put in place
handles this, we don't get any name clashes.
Andrew
Powered by blists - more mailing lists