[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2b8dbe95-c7e9-5158-93f6-865306a661b0@gmail.com>
Date: Tue, 30 May 2023 10:09:28 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Christian Marangi <ansuelsmth@...il.com>, Jonathan Corbet <corbet@....net>
Cc: Pavel Machek <pavel@....cz>, Lee Jones <lee@...nel.org>,
Andrew Lunn <andrew@...n.ch>, Florian Fainelli <f.fainelli@...il.com>,
Vladimir Oltean <olteanv@...il.com>, "David S. Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
linux-leds@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [net-next PATCH v3 03/13] Documentation: leds: leds-class:
Document new Hardware driven LEDs APIs
On 5/29/23 21:09, Christian Marangi wrote:
> Just to clarify, a device name can't be returned. Not every device have
> a name and such name can be changed. An example is network device where
> you can change the name of the interface.
>
> Using the device prevents all of this problem.
>
Oh, I guess it was /dev/something.
--
An old man doll... just what I always wanted! - Clara
Powered by blists - more mailing lists