From: Simon Horman <horms@kernel.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, saeedm@nvidia.com,
leon@kernel.org, tariqt@nvidia.com, andrew+netdev@lunn.ch,
donald.hunter@gmail.com, parav@nvidia.com
Subject: Re: [PATCH net-next 3/4] devlink: add function unique identifier to devlink dev info
Date: Sun, 23 Mar 2025 17:18:56 +0000 [thread overview]
Message-ID: <20250323171856.GW892515@horms.kernel.org> (raw)
In-Reply-To: <20250318153627.95030-4-jiri@resnulli.us>
On Tue, Mar 18, 2025 at 04:36:26PM +0100, Jiri Pirko wrote:
> From: Jiri Pirko <jiri@nvidia.com>
>
> Presently, for multi-PF NIC each PF reports the same serial_number and
> board.serial_number.
>
> To universally identify a function, add function unique identifier (uid)
> to be obtained from the driver as a string of arbitrary length.
>
> Signed-off-by: Jiri Pirko <jiri@nvidia.com>
> Reviewed-by: Parav Pandit <parav@nvidia.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2025-03-23 17:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 15:36 [PATCH net-next 0/4] net/mlx5: Expose additional devlink dev info Jiri Pirko
2025-03-18 15:36 ` [PATCH net-next 1/4] ynl: devlink: add missing board-serial-number Jiri Pirko
2025-03-23 17:18 ` Simon Horman
2025-03-18 15:36 ` [PATCH net-next 2/4] net/mlx5: Expose serial numbers in devlink info Jiri Pirko
2025-03-18 17:38 ` Simon Horman
2025-03-19 11:39 ` Jiri Pirko
2025-03-20 13:50 ` Simon Horman
2025-03-23 17:18 ` Simon Horman
2025-03-18 15:36 ` [PATCH net-next 3/4] devlink: add function unique identifier to devlink dev info Jiri Pirko
2025-03-23 17:18 ` Simon Horman [this message]
2025-03-18 15:36 ` [PATCH net-next 4/4] net/mlx5: Expose function UID in devlink info Jiri Pirko
2025-03-23 17:19 ` Simon Horman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250323171856.GW892515@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=parav@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).