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, dsahern@kernel.org
Subject: Re: [PATCH net-next 0/2] ipv4: Remove RT_CONN_FLAGS() calls in flowi4_init_output().
Date: Wed, 07 Jun 2023 04:20:24 +0000 [thread overview]
Message-ID: <168611162445.32150.17616094899145793582.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1685999117.git.gnault@redhat.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 5 Jun 2023 23:55:19 +0200 you wrote:
> Remove a few RT_CONN_FLAGS() calls used inside flowi4_init_output().
> These users can be easily converted to set the scope properly, instead
> of overloading the tos parameter with scope information as done by
> RT_CONN_FLAGS().
>
> The objective is to eventually remove RT_CONN_FLAGS() entirely, which
> will then allow to also remove RTO_ONLINK and to finally convert
> ->flowi4_tos to dscp_t.
>
> [...]
Here is the summary with links:
- [net-next,1/2] ipv4: Set correct scope in inet_csk_route_*().
https://git.kernel.org/netdev/net-next/c/4b095281caca
- [net-next,2/2] tcp: Set route scope properly in cookie_v4_check().
https://git.kernel.org/netdev/net-next/c/6f8a76f80221
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:[~2023-06-07 4:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 21:55 [PATCH net-next 0/2] ipv4: Remove RT_CONN_FLAGS() calls in flowi4_init_output() Guillaume Nault
2023-06-05 21:55 ` [PATCH net-next 1/2] ipv4: Set correct scope in inet_csk_route_*() Guillaume Nault
2023-06-06 2:47 ` David Ahern
2023-06-05 21:55 ` [PATCH net-next 2/2] tcp: Set route scope properly in cookie_v4_check() Guillaume Nault
2023-06-06 2:47 ` David Ahern
2023-06-07 4:20 ` 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=168611162445.32150.17616094899145793582.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=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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).