[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b85b14c1-611c-4002-8fc9-cf23bc849799@lunn.ch>
Date: Wed, 26 Feb 2025 15:57:33 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Shenwei Wang <shenwei.wang@....com>
Cc: Claudiu Manoil <claudiu.manoil@....com>,
Vladimir Oltean <vladimir.oltean@....com>,
Wei Fang <wei.fang@....com>, Clark Wang <xiaoning.wang@....com>,
Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
imx@...ts.linux.dev, netdev@...r.kernel.org, linux-imx@....com
Subject: Re: [PATCH net-next] net: enetc: Support ethernet aliases in dts.
On Tue, Feb 25, 2025 at 03:44:58PM -0600, Shenwei Wang wrote:
> Retrieve the "ethernet" alias ID from the DTS and assign it as the
> interface name (e.g., "eth0", "eth1"). This ensures predictable naming
> aligned with the DTS's configuration.
>
> If no alias is defined, fall back to the kernel's default enumeration
> to maintain backward compatibility.
GregKH and others will tell you this is a user space problem. Ethernet
names have never been stable, user space has always had to deal with
this problem. Please use a udev rule, systemd naming, etc.
Andrew
Powered by blists - more mailing lists