All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@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,
	horms@kernel.org, donald.hunter@gmail.com, parav@nvidia.com
Subject: Re: [PATCH net-next v2 0/4] net/mlx5: Expose additional devlink dev info
Date: Tue, 25 Mar 2025 12:00:31 +0000	[thread overview]
Message-ID: <174290403176.534907.13973863538007744367.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250320085947.103419-1-jiri@resnulli.us>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 20 Mar 2025 09:59:43 +0100 you wrote:
> From: Jiri Pirko <jiri@nvidia.com>
> 
> This patchset aims to expose couple of already defined serial numbers
> for mlx5 driver.
> 
> On top of that, it introduces new field, "function.uid" and exposes
> that for mlx5 driver.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/4] ynl: devlink: add missing board-serial-number
    https://git.kernel.org/netdev/net-next/c/3e25c1a7c056
  - [net-next,v2,2/4] net/mlx5: Expose serial numbers in devlink info
    (no matching commit)
  - [net-next,v2,3/4] devlink: add function unique identifier to devlink dev info
    (no matching commit)
  - [net-next,v2,4/4] net/mlx5: Expose function UID in devlink info
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-03-25 11:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-20  8:59 [PATCH net-next v2 0/4] net/mlx5: Expose additional devlink dev info Jiri Pirko
2025-03-20  8:59 ` [PATCH net-next v2 1/4] ynl: devlink: add missing board-serial-number Jiri Pirko
2025-03-23 17:47   ` Simon Horman
2025-03-24  4:08   ` Kalesh Anakkur Purayil
2025-03-20  8:59 ` [PATCH net-next v2 2/4] net/mlx5: Expose serial numbers in devlink info Jiri Pirko
2025-03-23 17:47   ` Simon Horman
2025-03-24  4:07   ` Kalesh Anakkur Purayil
2025-03-25 11:46   ` Jakub Kicinski
2025-03-31 13:06     ` Jiri Pirko
2025-03-31 16:22       ` Jakub Kicinski
2025-04-01  9:01         ` Jiri Pirko
2025-04-01 14:52           ` Jakub Kicinski
2025-03-20  8:59 ` [PATCH net-next v2 3/4] devlink: add function unique identifier to devlink dev info Jiri Pirko
2025-03-23 17:47   ` Simon Horman
2025-03-24  4:06   ` Kalesh Anakkur Purayil
2025-03-25 11:49   ` Jakub Kicinski
2025-03-20  8:59 ` [PATCH net-next v2 4/4] net/mlx5: Expose function UID in devlink info Jiri Pirko
2025-03-23 17:48   ` Simon Horman
2025-03-24  4:05   ` Kalesh Anakkur Purayil
2025-03-23 12:00 ` [PATCH net-next v2 0/4] net/mlx5: Expose additional devlink dev info Tariq Toukan
2025-03-25 12:00 ` patchwork-bot+netdevbpf [this message]

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=174290403176.534907.13973863538007744367.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.