From: patchwork-bot+netdevbpf@kernel.org
To: Guillaume Nault <gnault@redhat.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, netdev@vger.kernel.org, horms@kernel.org,
dsahern@kernel.org, jchapman@katalix.com, tparkin@katalix.com
Subject: Re: [PATCH net-next 0/5] ipv4: Consolidate route lookups from IPv4 sockets.
Date: Fri, 20 Dec 2024 22:10:31 +0000 [thread overview]
Message-ID: <173473263127.3034452.1670644709350879348.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1734357769.git.gnault@redhat.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.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
prev parent reply other threads:[~2024-12-20 22:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 17:21 [PATCH net-next 0/5] ipv4: Consolidate route lookups from IPv4 sockets Guillaume Nault
2024-12-16 17:21 ` [PATCH net-next 1/5] ipv4: Define inet_sk_init_flowi4() and use it in inet_sk_rebuild_header() Guillaume Nault
2024-12-16 17:21 ` [PATCH net-next 2/5] ipv4: Use inet_sk_init_flowi4() in ip4_datagram_release_cb() Guillaume Nault
2024-12-16 17:21 ` [PATCH net-next 3/5] ipv4: Use inet_sk_init_flowi4() in inet_csk_rebuild_route() Guillaume Nault
2024-12-16 17:21 ` [PATCH net-next 4/5] ipv4: Use inet_sk_init_flowi4() in __ip_queue_xmit() Guillaume Nault
2024-12-16 17:21 ` [PATCH net-next 5/5] l2tp: Use inet_sk_init_flowi4() in l2tp_ip_sendmsg() Guillaume Nault
2024-12-17 8:00 ` James Chapman
2024-12-20 22:10 ` 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=173473263127.3034452.1670644709350879348.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=horms@kernel.org \
--cc=jchapman@katalix.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tparkin@katalix.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.