[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id:
<171257890235.8472.12307217868929913978.git-patchwork-notify@kernel.org>
Date: Mon, 08 Apr 2024 12:21:42 +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, mustafa.ismail@...el.com,
shiraz.saleem@...el.com, jgg@...pe.ca, leon@...nel.org,
mkalderon@...vell.com, aelior@...vell.com, j.vosburgh@...il.com,
andy@...yhouse.net, dsahern@...nel.org, kadlec@...filter.org,
roopa@...dia.com, razor@...ckwall.org
Subject: Re: [PATCH net-next] ipv4: Set scope explicitly in ip_route_output().
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@...emloft.net>:
On Fri, 5 Apr 2024 22:05:00 +0200 you wrote:
> Add a "scope" parameter to ip_route_output() so that callers don't have
> to override the tos parameter with the RTO_ONLINK flag if they want a
> local scope.
>
> This will allow converting flowi4_tos to dscp_t in the future, thus
> allowing static analysers to flag invalid interactions between
> "tos" (the DSCP bits) and ECN.
>
> [...]
Here is the summary with links:
- [net-next] ipv4: Set scope explicitly in ip_route_output().
https://git.kernel.org/netdev/net-next/c/ec20b2830093
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