From: patchwork-bot+netdevbpf@kernel.org
To: Leon Romanovsky <leon@kernel.org>
Cc: jgg@nvidia.com, pabeni@redhat.com, kuba@kernel.org,
davem@davemloft.net, saeedm@nvidia.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [GIT PULL] Please pull mlx5-next changes
Date: Thu, 16 Feb 2023 19:40:34 +0000 [thread overview]
Message-ID: <167657643420.21159.10847582499249880114.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230215095624.1365200-1-leon@kernel.org>
Hello:
This pull request was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 15 Feb 2023 11:56:24 +0200 you wrote:
> Hi Jason,
>
> Following previous conversations [1] and our clear commitment to do the TC work [2],
> please pull mlx5-next shared branch, which includes low-level steering logic to allow
> RoCEv2 traffic to be encrypted/decrypted through IPsec.
>
> Thanks
>
> [...]
Here is the summary with links:
- [GIT,PULL] Please pull mlx5-next changes
https://git.kernel.org/netdev/net-next/c/84cb1b53cdba
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-02-16 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 9:56 [GIT PULL] Please pull mlx5-next changes Leon Romanovsky
2023-02-16 19:37 ` Jakub Kicinski
2023-02-19 9:05 ` Leon Romanovsky
2023-02-16 19:40 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-09 5:53 Leon Romanovsky
2022-04-12 3:50 ` patchwork-bot+netdevbpf
2022-04-12 13:57 ` Jason Gunthorpe
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=167657643420.21159.10847582499249880114.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=jgg@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).