[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241107204157.683bca11@kernel.org>
Date: Thu, 7 Nov 2024 20:41:57 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Khang Nguyen <khangng@...amperecomputing.com>
Cc: Jeremy Kerr <jk@...econstruct.com.au>, Matt Johnston
<matt@...econstruct.com.au>, Andrew Lunn <andrew+netdev@...n.ch>, "David S.
Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo
Abeni <pabeni@...hat.com>, Simon Horman <horms@...nel.org>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
ampere-linux-kernel@...ts.amperecomputing.com, Phong Vo
<phong@...amperecomputing.com>, Thang Nguyen
<thang@...amperecomputing.com>, Khanh Pham <khpham@...erecomputing.com>,
Phong Vo <pvo@...erecomputing.com>, Quan Nguyen
<quan@...amperecomputing.com>, Chanh Nguyen <chanh@...amperecomputing.com>,
Thu Nguyen <thu@...amperecomputing.com>, Hieu Le
<hieul@...erecomputing.com>, openbmc@...ts.ozlabs.org,
patches@...erecomputing.com
Subject: Re: [PATCH net-next] net: mctp: Expose transport binding identifier
via IFLA attribute
On Tue, 5 Nov 2024 14:19:15 +0700 Khang Nguyen wrote:
> However, we currently have no means to get this information from MCTP
> links.
I'm not opposed to the netlink attribute, but to be clear this info
is indirectly available in sysfs, right? We link the netdev to
the parent device so the type of /sys/class/net/$your_ifc/device
should reveal what the transport is?
Powered by blists - more mailing lists