From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, netdev@vger.kernel.org, saeedm@nvidia.com,
gal@nvidia.com, leonro@nvidia.com
Subject: Re: [PATCH net 0/2] geneve fixes
Date: Mon, 10 Jun 2024 12:20:33 +0000 [thread overview]
Message-ID: <171802203330.2008.15446674732099700467.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240606203249.1054066-1-tariqt@nvidia.com>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 6 Jun 2024 23:32:47 +0300 you wrote:
> Hi,
>
> This small patchset by Gal provides bug fixes to the geneve tunnels flows.
>
> Patch 1 fixes an incorrect value returned by the inner network header
> offset helper.
> Patch 2 fixes an issue inside the mlx5e tunneling flow. It 'happened' to
> be harmless so far, before applying patch 1.
>
> [...]
Here is the summary with links:
- [net,1/2] geneve: Fix incorrect inner network header offset when innerprotoinherit is set
https://git.kernel.org/netdev/net/c/c6ae073f5903
- [net,2/2] net/mlx5e: Fix features validation check for tunneled UDP (non-VXLAN) packets
https://git.kernel.org/netdev/net/c/791b4089e326
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-06-10 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 20:32 [PATCH net 0/2] geneve fixes Tariq Toukan
2024-06-06 20:32 ` [PATCH net 1/2] geneve: Fix incorrect inner network header offset when innerprotoinherit is set Tariq Toukan
2024-06-07 11:10 ` Wojciech Drewek
2024-06-06 20:32 ` [PATCH net 2/2] net/mlx5e: Fix features validation check for tunneled UDP (non-VXLAN) packets Tariq Toukan
2024-06-07 11:13 ` Wojciech Drewek
2024-06-10 12: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=171802203330.2008.15446674732099700467.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.