From: patchwork-bot+netdevbpf@kernel.org
To: Matthias May <matthias.may@westermo.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
yoshfuji@linux-ipv6.org, dsahern@kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, nicolas.dichtel@6wind.com,
eyal.birger@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] ip_tunnels: allow VXLAN/GENEVE to inherit TOS/TTL from VLAN
Date: Sat, 23 Jul 2022 05:00:14 +0000 [thread overview]
Message-ID: <165855241426.3532.9698805298871914394.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220721202718.10092-1-matthias.may@westermo.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 21 Jul 2022 22:27:19 +0200 you wrote:
> The current code allows for VXLAN and GENEVE to inherit the TOS
> respective the TTL when skb-protocol is ETH_P_IP or ETH_P_IPV6.
> However when the payload is VLAN encapsulated, then this inheriting
> does not work, because the visible skb-protocol is of type
> ETH_P_8021Q or ETH_P_8021AD.
>
> Instead of skb->protocol use skb_protocol().
>
> [...]
Here is the summary with links:
- [net-next] ip_tunnels: allow VXLAN/GENEVE to inherit TOS/TTL from VLAN
https://git.kernel.org/netdev/net-next/c/7074732c8fae
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:[~2022-07-23 5:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 20:27 [PATCH net-next] ip_tunnels: allow VXLAN/GENEVE to inherit TOS/TTL from VLAN Matthias May
2022-07-23 5: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=165855241426.3532.9698805298871914394.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=eyal.birger@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.may@westermo.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.com \
--cc=yoshfuji@linux-ipv6.org \
/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