public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Gavin Li <gavinl@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, roopa@nvidia.com,
	eng.alaamohamedsoliman.am@gmail.com, bigeasy@linutronix.de,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	gavi@nvidia.com, roid@nvidia.com, maord@nvidia.com,
	saeedm@nvidia.com
Subject: Re: [PATCH net-next v8 0/5] net/mlx5e: Add GBP VxLAN HW offload support
Date: Sat, 18 Mar 2023 05:50:21 +0000	[thread overview]
Message-ID: <167911862106.13068.1349424509665979718.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230316070758.83512-1-gavinl@nvidia.com>

Hello:

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

On Thu, 16 Mar 2023 09:07:53 +0200 you wrote:
> Patch-1: Remove unused argument from functions.
> Patch-2: Expose helper function vxlan_build_gbp_hdr.
> Patch-3: Add helper function for encap_info_equal for tunnels with options.
> Patch-4: Preserving the const-ness of the pointer in ip_tunnel_info_opts.
> Patch-5: Add HW offloading support for TC flows with VxLAN GBP encap/decap
>         in mlx ethernet driver.
> 
> [...]

Here is the summary with links:
  - [net-next,v8,1/5] vxlan: Remove unused argument from vxlan_build_gbp_hdr( ) and vxlan_build_gpe_hdr( )
    https://git.kernel.org/netdev/net-next/c/df5e87f16c33
  - [net-next,v8,2/5] vxlan: Expose helper vxlan_build_gbp_hdr
    https://git.kernel.org/netdev/net-next/c/c641e9279f35
  - [net-next,v8,3/5] net/mlx5e: Add helper for encap_info_equal for tunnels with options
    https://git.kernel.org/netdev/net-next/c/58de53c10258
  - [net-next,v8,4/5] ip_tunnel: Preserve pointer const in ip_tunnel_info_opts
    https://git.kernel.org/netdev/net-next/c/bc9d003dc48c
  - [net-next,v8,5/5] net/mlx5e: TC, Add support for VxLAN GBP encap/decap flows offload
    https://git.kernel.org/netdev/net-next/c/6ee44c518159

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



      parent reply	other threads:[~2023-03-18  5:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16  7:07 [PATCH net-next v8 0/5] net/mlx5e: Add GBP VxLAN HW offload support Gavin Li
2023-03-16  7:07 ` [PATCH net-next v8 1/5] vxlan: Remove unused argument from vxlan_build_gbp_hdr( ) and vxlan_build_gpe_hdr( ) Gavin Li
2023-03-16  7:07 ` [PATCH net-next v8 2/5] vxlan: Expose helper vxlan_build_gbp_hdr Gavin Li
2023-03-16  7:07 ` [PATCH net-next v8 3/5] net/mlx5e: Add helper for encap_info_equal for tunnels with options Gavin Li
2023-03-16  7:07 ` [PATCH net-next v8 4/5] ip_tunnel: Preserve pointer const in ip_tunnel_info_opts Gavin Li
2023-03-16  7:07 ` [PATCH net-next v8 5/5] net/mlx5e: TC, Add support for VxLAN GBP encap/decap flows offload Gavin Li
2023-03-18  5:50 ` 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=167911862106.13068.1349424509665979718.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eng.alaamohamedsoliman.am@gmail.com \
    --cc=gavi@nvidia.com \
    --cc=gavinl@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maord@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=roid@nvidia.com \
    --cc=roopa@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