[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3470cae3-d86c-4dd5-a24c-c7f4bf6e017a@oss.qualcomm.com>
Date: Wed, 10 Dec 2025 12:00:25 +0530
From: vivek pernamitta <vivek.pernamitta@....qualcomm.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: 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>,
Manivannan Sadhasivam <mani@...nel.org>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, mhi@...ts.linux.dev,
linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH v6 1/2] net: mhi: Enable Ethernet interface support
On 12/9/2025 7:06 PM, Andrew Lunn wrote:
>> ndev = alloc_netdev(sizeof(struct mhi_net_dev), info->netname,
>> - NET_NAME_PREDICTABLE, mhi_net_setup);
>> + NET_NAME_PREDICTABLE, info->ethernet_if ?
>> + mhi_ethernet_setup : mhi_net_setup);
>
> Is the name predictable? I thought "eth%d" was considered
> NET_NAME_ENUM?
>
> https://elixir.bootlin.com/linux/v6.18/source/net/ethernet/eth.c#L382
>
> Andrew
For Ethernet-type devices, the interface name will follow the standard
convention: eth%d, For normal IP interfaces, the interface will be
created as mhi_swip%d/mhi_hwip%d.The naming will depend on the details
provided through |struct mhi_device_info.|
Powered by blists - more mailing lists