All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Saeed Mahameed <saeed@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, jgg@nvidia.com, saeedm@nvidia.com,
	linux-rdma@vger.kernel.org, leonro@nvidia.com,
	netdev@vger.kernel.org, mbloch@nvidia.com, tariqt@nvidia.com,
	daniel.zahka@gmail.com, raeds@nvidia.com
Subject: Re: [PATCH 1/1] net/mlx5: Add PSP capabilities structures and bits
Date: Wed, 03 Sep 2025 22:10:06 +0000	[thread overview]
Message-ID: <175693740626.1217361.17270265115984686138.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250903063050.668442-2-saeed@kernel.org>

Hello:

This patch was applied to netdev/net-next.git (main)
by Saeed Mahameed <saeedm@nvidia.com>:

On Tue,  2 Sep 2025 23:30:50 -0700 you wrote:
> From: Saeed Mahameed <saeedm@nvidia.com>
> 
> Add mlx5_ifc PSP related capabilities structures and HW definitions
> needed for PSP support in mlx5.
> 
> Link: https://lore.kernel.org/netdev/20250828162953.2707727-1-daniel.zahka@gmail.com/
> Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
> 
> [...]

Here is the summary with links:
  - [1/1] net/mlx5: Add PSP capabilities structures and bits
    https://git.kernel.org/netdev/net-next/c/04a3134f88a4

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



  reply	other threads:[~2025-09-03 22:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-03  6:30 [GIT PULL] mlx5 PSP IFC bits Saeed Mahameed
2025-09-03  6:30 ` [PATCH 1/1] net/mlx5: Add PSP capabilities structures and bits Saeed Mahameed
2025-09-03 22:10   ` patchwork-bot+netdevbpf [this message]
2025-09-03 22:10 ` [GIT PULL] mlx5 PSP IFC bits patchwork-bot+netdevbpf

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=175693740626.1217361.17270265115984686138.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=daniel.zahka@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jgg@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=leonro@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=raeds@nvidia.com \
    --cc=saeed@kernel.org \
    --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.