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,
willemdebruijn.kernel@gmail.com
Subject: Re: [PATCH net-next 0/3] ipv4: Remove RTO_ONLINK from udp, ping and raw sockets.
Date: Wed, 24 May 2023 07:30:21 +0000 [thread overview]
Message-ID: <168491342110.25320.5576599970370486815.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1684764727.git.gnault@redhat.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Mon, 22 May 2023 16:37:50 +0200 you wrote:
> udp_sendmsg(), ping_v4_sendmsg() and raw_sendmsg() use similar patterns
> for restricting their route lookup to on-link hosts. Although they use
> slightly different code, they all use RTO_ONLINK to override the least
> significant bit of their tos value.
>
> RTO_ONLINK is used to restrict the route scope even when the scope is
> set to RT_SCOPE_UNIVERSE. Therefore it isn't necessary: we can properly
> set the scope to RT_SCOPE_LINK instead.
>
> [...]
Here is the summary with links:
- [net-next,1/3] ping: Stop using RTO_ONLINK.
https://git.kernel.org/netdev/net-next/c/726de790f660
- [net-next,2/3] raw: Stop using RTO_ONLINK.
https://git.kernel.org/netdev/net-next/c/c85be08fc4fa
- [net-next,3/3] udp: Stop using RTO_ONLINK.
https://git.kernel.org/netdev/net-next/c/0e26371db548
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-05-24 7:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 14:37 [PATCH net-next 0/3] ipv4: Remove RTO_ONLINK from udp, ping and raw sockets Guillaume Nault
2023-05-22 14:37 ` [PATCH net-next 1/3] ping: Stop using RTO_ONLINK Guillaume Nault
2023-05-23 15:09 ` David Ahern
2023-05-22 14:38 ` [PATCH net-next 2/3] raw: " Guillaume Nault
2023-05-23 15:13 ` David Ahern
2023-05-22 14:38 ` [PATCH net-next 3/3] udp: " Guillaume Nault
2023-05-23 15:14 ` David Ahern
2023-05-24 7:30 ` 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=168491342110.25320.5576599970370486815.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 \
--cc=willemdebruijn.kernel@gmail.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).