[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <hjhpopnmorqqo65mw7psmlzmqvzhn2d6x22y2aq5miqsevdkmi@oak2s6kxfght>
Date: Mon, 28 Jul 2025 10:06:56 +0200
From: Jiri Pirko <jiri@...nulli.us>
To: Marc Kleine-Budde <mkl@...gutronix.de>
Cc: netdev@...r.kernel.org, davem@...emloft.net, kuba@...nel.org,
linux-can@...r.kernel.org, kernel@...gutronix.de, Jimmy Assarsson <extja@...ser.com>,
Vincent Mailhol <mailhol.vincent@...adoo.fr>
Subject: Re: [PATCH net-next 26/27] can: kvaser_usb: Add devlink port support
Fri, Jul 25, 2025 at 06:05:36PM +0200, mkl@...gutronix.de wrote:
>From: Jimmy Assarsson <extja@...ser.com>
>
>Register each CAN channel of the device as an devlink physical port.
>This makes it easier to get device information for a given network
>interface (i.e. can2).
>
>Example output:
> $ devlink dev
> usb/1-1.3:1.0
>
> $ devlink port
> usb/1-1.3:1.0/0: type eth netdev can0 flavour physical port 0 splittable false
> usb/1-1.3:1.0/1: type eth netdev can1 flavour physical port 1 splittable false
>
> $ devlink port show can1
> usb/1-1.3:1.0/1: type eth netdev can1 flavour physical port 0 splittable false
Looks fine to me. Out of curiosity, do you have some plans to extend use
of devlink port in the future, or this is it?
Powered by blists - more mailing lists