[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210721182502.GB7554@duo.ucw.cz>
Date: Wed, 21 Jul 2021 20:25:02 +0200
From: Pavel Machek <pavel@....cz>
To: Andrew Lunn <andrew@...n.ch>, marek.behun@....cz
Cc: Heiner Kallweit <hkallweit1@...il.com>,
Tony Nguyen <anthony.l.nguyen@...el.com>, davem@...emloft.net,
kuba@...nel.org, Kurt Kanzenbach <kurt@...utronix.de>,
netdev@...r.kernel.org, sasha.neftin@...el.com,
vitaly.lifshits@...el.com, vinicius.gomes@...el.com,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Dvora Fuxbrumer <dvorax.fuxbrumer@...ux.intel.com>,
"linux-leds@...r.kernel.org" <linux-leds@...r.kernel.org>
Subject: Re: [PATCH net-next 5/5] igc: Export LEDs
Hi!
> > > Now the (linked) LED devices are under /sys/class/net/<ifname>, but still
> > > the primary LED devices are under /sys/class/leds and their names have
> > > to be unique therefore. The LED subsystem takes care of unique names,
> > > but in case of a second network interface the LED device name suddenly
> > > would be led0_1 (IIRC). So the names wouldn't be predictable, and I think
> > > that's not what we want.
> >
> > We need input from the LED maintainers, but do we actually need the
> > symbolic links in /sys/class/leds/? For this specific use case, not
> > generally. Allow an LED to opt out of the /sys/class/leds symlink.
> >
> > If we could drop those, we can relax the naming requirements so that
> > the names is unique to a parent device, not globally unique.
>
> Well, I believe we already negotiated acceptable naming with
> Marek... Is it unsuitable for some reason?
Sorry, hit send too soon.. Marek is now in cc list.
Pavel
--
http://www.livejournal.com/~pavelmachek
Download attachment "signature.asc" of type "application/pgp-signature" (196 bytes)
Powered by blists - more mailing lists