[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<168976682016.23748.15879521041642434800.git-patchwork-notify@kernel.org>
Date: Wed, 19 Jul 2023 11:40:20 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Guillaume Nault <gnault@...hat.com>
Cc: davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com,
edumazet@...gle.com, netdev@...r.kernel.org, pablo@...filter.org,
laforge@...monks.org, osmocom-net-gprs@...ts.osmocom.org,
dccp@...r.kernel.org, marcelo.leitner@...il.com, lucien.xin@...il.com,
linux-sctp@...r.kernel.org
Subject: Re: [PATCH net-next 0/3] net: Remove more RTO_ONLINK users.
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@...emloft.net>:
On Mon, 17 Jul 2023 15:53:24 +0200 you wrote:
> Code that initialise a flowi4 structure manually before doing a fib
> lookup can easily avoid overloading ->flowi4_tos with the RTO_ONLINK
> bit. They can just set ->flowi4_scope correctly instead.
>
> Properly separating the routing scope from ->flowi4_tos will allow to
> eventually convert this field to dscp_t (to ensure proper separation
> between DSCP and ECN).
>
> [...]
Here is the summary with links:
- [net-next,1/3] gtp: Set TOS and routing scope independently for fib lookups.
https://git.kernel.org/netdev/net-next/c/b16b50476714
- [net-next,2/3] dccp: Set TOS and routing scope independently for fib lookups.
https://git.kernel.org/netdev/net-next/c/2d6c85ca3eb8
- [net-next,3/3] sctp: Set TOS and routing scope independently for fib lookups.
https://git.kernel.org/netdev/net-next/c/ba80e20d7f3f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists