public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Leon Romanovsky <leon@kernel•org>
Cc: jgg@nvidia•com, davem@davemloft•net, kuba@kernel•org,
	pabeni@redhat•com, edumazet@google•com,
	linux-rdma@vger•kernel.org, mbloch@nvidia•com,
	netdev@vger•kernel.org, phaddad@nvidia•com, saeedm@nvidia•com,
	steffen.klassert@secunet•com, horms@kernel•org
Subject: Re: [GIT PULL] Please pull IPsec packet offload support in multiport RoCE devices
Date: Fri, 13 Oct 2023 17:00:25 +0000	[thread overview]
Message-ID: <169721642579.16770.13380913448246325654.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231002083832.19746-1-leon@kernel.org>

Hello:

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

On Mon,  2 Oct 2023 11:38:31 +0300 you wrote:
> Hi,
> 
> This PR is collected from https://lore.kernel.org/all/cover.1695296682.git.leon@kernel.org
> 
> This series from Patrisious extends mlx5 to support IPsec packet offload
> in multiport devices (MPV, see [1] for more details).
> 
> [...]

Here is the summary with links:
  - [GIT,PULL] Please pull IPsec packet offload support in multiport RoCE devices
    https://git.kernel.org/netdev/net-next/c/1bc60524ca1a

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



      reply	other threads:[~2023-10-13 17:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-02  8:38 [GIT PULL] Please pull IPsec packet offload support in multiport RoCE devices Leon Romanovsky
2023-10-13 17: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=169721642579.16770.13380913448246325654.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=horms@kernel$(echo .)org \
    --cc=jgg@nvidia$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=leon@kernel$(echo .)org \
    --cc=linux-rdma@vger$(echo .)kernel.org \
    --cc=mbloch@nvidia$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=phaddad@nvidia$(echo .)com \
    --cc=saeedm@nvidia$(echo .)com \
    --cc=steffen.klassert@secunet$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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