netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Leon Romanovsky <leon@kernel.org>
Cc: jgg@nvidia.com, kuba@kernel.org, davem@davemloft.net,
	edumazet@google.com, linux-rdma@vger.kernel.org,
	maorg@nvidia.com, markzhang@nvidia.com, netdev@vger.kernel.org,
	pabeni@redhat.com, phaddad@nvidia.com, raeds@nvidia.com,
	saeedm@nvidia.com, horms@kernel.org
Subject: Re: [GIT PULL v1] Please pull mlx5 MACsec RoCEv2 support
Date: Thu, 24 Aug 2023 19:10:26 +0000	[thread overview]
Message-ID: <169290422609.11645.14718872759290823619.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230821073833.59042-1-leon@kernel.org>

Hello:

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

On Mon, 21 Aug 2023 10:38:25 +0300 you wrote:
> Changelog:
> v1:
>  * Removed NULL check in first macsec patch as it is not needed.
>  * Added more information about potential merge conflict.
> v0: https://lore.kernel.org/netdev/20230813064703.574082-1-leon@kernel.org/
> ----------------------------------------------------------------
> 
> [...]

Here is the summary with links:
  - [GIT,PULL,v1] Please pull mlx5 MACsec RoCEv2 support
    https://git.kernel.org/netdev/net-next/c/3c5066c6b0a5

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



      reply	other threads:[~2023-08-24 19:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-21  7:38 [GIT PULL v1] Please pull mlx5 MACsec RoCEv2 support Leon Romanovsky
2023-08-24 19: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=169290422609.11645.14718872759290823619.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jgg@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=maorg@nvidia.com \
    --cc=markzhang@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=phaddad@nvidia.com \
    --cc=raeds@nvidia.com \
    --cc=saeedm@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).