[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6db5b691-a1cb-4f74-bb0d-6b48a1678c65@lunn.ch>
Date: Tue, 30 May 2023 14:24:48 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Bagas Sanjaya <bagasdotme@...il.com>
Cc: Christian Marangi <ansuelsmth@...il.com>,
Jonathan Corbet <corbet@....net>, Pavel Machek <pavel@....cz>,
Lee Jones <lee@...nel.org>, 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 Tue, May 30, 2023 at 10:09:28AM +0700, Bagas Sanjaya wrote:
> 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.
Network devices don't appear in /dev. At least not in Linux. Some
other Unix implementations do, i think SunOS used to have an entry in
/dev, but i could be remembering wrongly.
But within the kernel, you generally don't refer to a device by its
/dev/foo name. That is a user space abstraction. In the kernel, each
device in the system has a struct device representing it.
Andrew
Powered by blists - more mailing lists