netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Leon Romanovsky <leon@kernel.org>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, horms@kernel.org, markzhang@nvidia.com,
	netdev@vger.kernel.org, pabeni@redhat.com, phaddad@nvidia.com,
	tariqt@nvidia.com
Subject: Re: [PATCH net-next v1] net/mlx4e: Don't redefine IB_MTU_XXX enum
Date: Wed, 18 Jun 2025 21:20:19 +0000	[thread overview]
Message-ID: <175028161948.259999.14361453597066990153.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <382c91ee506e7f1f3c1801957df6b28963484b7d.1750147222.git.leon@kernel.org>

Hello:

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

On Tue, 17 Jun 2025 11:06:30 +0300 you wrote:
> From: Mark Zhang <markzhang@nvidia.com>
> 
> Rely on existing IB_MTU_XXX definitions which exist in ib_verbs.h.
> 
> Reviewed-by: Patrisious Haddad <phaddad@nvidia.com>
> Signed-off-by: Mark Zhang <markzhang@nvidia.com>
> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> 
> [...]

Here is the summary with links:
  - [net-next,v1] net/mlx4e: Don't redefine IB_MTU_XXX enum
    https://git.kernel.org/netdev/net-next/c/e0e3265acf5a

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-06-18 21:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17  8:06 [PATCH net-next v1] net/mlx4e: Don't redefine IB_MTU_XXX enum Leon Romanovsky
2025-06-17 11:37 ` Simon Horman
2025-06-18 21:20 ` 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=175028161948.259999.14361453597066990153.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=markzhang@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=phaddad@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).