From: patchwork-bot+netdevbpf@kernel.org
To: Matthias May <matthias.may@westermo.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, roopa@nvidia.com,
eng.alaamohamedsoliman.am@gmail.com, bigeasy@linutronix.de,
saeedm@nvidia.com, leon@kernel.org, roid@nvidia.com,
maord@nvidia.com, lariel@nvidia.com, vladbu@nvidia.com,
cmi@nvidia.com, gnault@redhat.com, yoshfuji@linux-ipv6.org,
dsahern@kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, linux-rdma@vger.kernel.org,
nicolas.dichtel@6wind.com, eyal.birger@gmail.com,
jesse@nicira.com, linville@tuxdriver.com, daniel@iogearbox.net,
hadarh@mellanox.com, ogerlitz@mellanox.com, willemb@google.com,
martin.varghese@nokia.com
Subject: Re: [PATCH v3 net 0/4] Do not use RT_TOS for IPv6 flowlabel
Date: Wed, 10 Aug 2022 05:30:15 +0000 [thread overview]
Message-ID: <166010941509.28354.4070205529525758568.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220805191906.9323-1-matthias.may@westermo.com>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 5 Aug 2022 21:19:02 +0200 you wrote:
> According to Guillaume Nault RT_TOS should never be used for IPv6.
>
> Quote:
> RT_TOS() is an old macro used to interprete IPv4 TOS as described in
> the obsolete RFC 1349. It's conceptually wrong to use it even in IPv4
> code, although, given the current state of the code, most of the
> existing calls have no consequence.
>
> [...]
Here is the summary with links:
- [v3,net,1/4] geneve: do not use RT_TOS for IPv6 flowlabel
https://git.kernel.org/netdev/net/c/ca2bb69514a8
- [v3,net,2/4] vxlan: do not use RT_TOS for IPv6 flowlabel
https://git.kernel.org/netdev/net/c/e488d4f5d6e4
- [v3,net,3/4] mlx5: do not use RT_TOS for IPv6 flowlabel
https://git.kernel.org/netdev/net/c/bcb0da7fffee
- [v3,net,4/4] ipv6: do not use RT_TOS for IPv6 flowlabel
https://git.kernel.org/netdev/net/c/ab7e2e0dfa5d
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-08-10 5:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 19:19 [PATCH v3 net 0/4] Do not use RT_TOS for IPv6 flowlabel Matthias May
2022-08-05 19:19 ` [PATCH v3 net 1/4] geneve: do " Matthias May
2022-08-05 19:19 ` [PATCH v3 net 2/4] vxlan: " Matthias May
2022-08-05 19:19 ` [PATCH v3 net 3/4] mlx5: " Matthias May
2022-08-05 19:19 ` [PATCH v3 net 4/4] ipv6: " Matthias May
2022-08-10 5:30 ` 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=166010941509.28354.4070205529525758568.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=bpf@vger.kernel.org \
--cc=cmi@nvidia.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=eng.alaamohamedsoliman.am@gmail.com \
--cc=eyal.birger@gmail.com \
--cc=gnault@redhat.com \
--cc=hadarh@mellanox.com \
--cc=jesse@nicira.com \
--cc=kuba@kernel.org \
--cc=lariel@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=maord@nvidia.com \
--cc=martin.varghese@nokia.com \
--cc=matthias.may@westermo.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=ogerlitz@mellanox.com \
--cc=pabeni@redhat.com \
--cc=roid@nvidia.com \
--cc=roopa@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=vladbu@nvidia.com \
--cc=willemb@google.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;
as well as URLs for NNTP newsgroup(s).