[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210810225353.6a19f772@thinkpad>
Date: Tue, 10 Aug 2021 22:53:53 +0200
From: Marek BehĂșn <kabel@...nel.org>
To: Pavel Machek <pavel@....cz>
Cc: Heiner Kallweit <hkallweit1@...il.com>,
Michael Walle <michael@...le.cc>, andrew@...n.ch,
anthony.l.nguyen@...el.com, bigeasy@...utronix.de,
davem@...emloft.net, dvorax.fuxbrumer@...ux.intel.com,
f.fainelli@...il.com, jacek.anaszewski@...il.com, kuba@...nel.org,
kurt@...utronix.de, linux-leds@...r.kernel.org,
netdev@...r.kernel.org, sasha.neftin@...el.com,
vinicius.gomes@...el.com, vitaly.lifshits@...el.com
Subject: Re: [PATCH net-next 5/5] igc: Export LEDs
On Tue, 10 Aug 2021 21:53:35 +0200
Pavel Machek <pavel@....cz> wrote:
> > Pavel, one point of the discussion is that in this case the LED is
> > controlled by MAC, not PHY. So the question is whether we want to do
> > "ethmacN" (in addition to "ethphyN").
>
> Sorry, I missed that. I guess that yes, ethmacX is okay, too.
>
> Even better would be to find common term that could be used for both
> ethmacN and ethphyN and just use that. (Except that we want to avoid
> ethX). Maybe "ethportX" would be suitable?
See
https://lore.kernel.org/linux-leds/YQAlPrF2uu3Gr+0d@lunn.ch/
and
https://lore.kernel.org/linux-leds/20210727172828.1529c764@thinkpad/
Marek
Powered by blists - more mailing lists