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, saeedm@nvidia.com, netdev@vger.kernel.org,
	tariqt@nvidia.com, gal@nvidia.com, leonro@nvidia.com,
	mbloch@nvidia.com
Subject: Re: [PATCH net-next] MAINTAINERS: Add myself as mlx5 core and mlx5e co-maintainer
Date: Mon, 30 Jun 2025 16:10:06 +0000	[thread overview]
Message-ID: <175129980651.3437924.8372418118753575516.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250627014252.1262592-1-saeed@kernel.org>

Hello:

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

On Thu, 26 Jun 2025 18:42:52 -0700 you wrote:
> From: Mark Bloch <mbloch@nvidia.com>
> 
> I have been working on mlx5 related code for several years,
> contributing features, code reviews, and occasional maintainer tasks
> when needed. This patch makes my maintainer role official.
> 
> Signed-off-by: Mark Bloch <mbloch@nvidia.com>
> Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
> 
> [...]

Here is the summary with links:
  - [net-next] MAINTAINERS: Add myself as mlx5 core and mlx5e co-maintainer
    https://git.kernel.org/netdev/net/c/60f7f4afaf6d

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



      reply	other threads:[~2025-06-30 16:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-27  1:42 [PATCH net-next] MAINTAINERS: Add myself as mlx5 core and mlx5e co-maintainer Saeed Mahameed
2025-06-30 16:10 ` 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=175129980651.3437924.8372418118753575516.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=leonro@nvidia.com \
    --cc=mbloch@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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.