[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<173473263127.3034452.1670644709350879348.git-patchwork-notify@kernel.org>
Date: Fri, 20 Dec 2024 22:10:31 +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, horms@...nel.org,
dsahern@...nel.org, jchapman@...alix.com, tparkin@...alix.com
Subject: Re: [PATCH net-next 0/5] ipv4: Consolidate route lookups from IPv4
sockets.
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Mon, 16 Dec 2024 18:21:40 +0100 you wrote:
> Create inet_sk_init_flowi4() so that the different IPv4 code paths that
> need to do a route lookup based on an IPv4 socket don't need to
> reimplement that logic.
>
> Guillaume Nault (5):
> ipv4: Define inet_sk_init_flowi4() and use it in
> inet_sk_rebuild_header().
> ipv4: Use inet_sk_init_flowi4() in ip4_datagram_release_cb().
> ipv4: Use inet_sk_init_flowi4() in inet_csk_rebuild_route().
> ipv4: Use inet_sk_init_flowi4() in __ip_queue_xmit().
> l2tp: Use inet_sk_init_flowi4() in l2tp_ip_sendmsg().
>
> [...]
Here is the summary with links:
- [net-next,1/5] ipv4: Define inet_sk_init_flowi4() and use it in inet_sk_rebuild_header().
https://git.kernel.org/netdev/net-next/c/1dbdce30f040
- [net-next,2/5] ipv4: Use inet_sk_init_flowi4() in ip4_datagram_release_cb().
https://git.kernel.org/netdev/net-next/c/5be1323b5041
- [net-next,3/5] ipv4: Use inet_sk_init_flowi4() in inet_csk_rebuild_route().
https://git.kernel.org/netdev/net-next/c/42e5ffc385f3
- [net-next,4/5] ipv4: Use inet_sk_init_flowi4() in __ip_queue_xmit().
https://git.kernel.org/netdev/net-next/c/148721f8e04a
- [net-next,5/5] l2tp: Use inet_sk_init_flowi4() in l2tp_ip_sendmsg().
https://git.kernel.org/netdev/net-next/c/c63e9f3b89d3
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