From: patchwork-bot+netdevbpf@kernel.org
To: Guillaume Nault <gnault@redhat.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
shuah@kernel.org, linux-kselftest@vger.kernel.org, fw@strlen.de
Subject: Re: [PATCH net-next] selftests: rtnetlink: Use more sensible tos values
Date: Fri, 04 Feb 2022 03:20:10 +0000 [thread overview]
Message-ID: <164394481045.31803.6913798555291608482.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <d61119e68d01ba7ef3ba50c1345a5123a11de123.1643815297.git.gnault@redhat.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 2 Feb 2022 16:24:21 +0100 you wrote:
> Using tos 0x1 with 'ip route get <IPv4 address> ...' doesn't test much
> of the tos option handling: 0x1 just sets an ECN bit, which is cleared
> by inet_rtm_getroute() before doing the fib lookup. Let's use 0x10
> instead, which is actually taken into account in the route lookup (and
> is less surprising for the reader).
>
> For consistency, use 0x10 for the IPv6 route lookup too (IPv6 currently
> doesn't clear ECN bits, but might do so in the future).
>
> [...]
Here is the summary with links:
- [net-next] selftests: rtnetlink: Use more sensible tos values
https://git.kernel.org/netdev/net-next/c/95eb6ef82b73
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:[~2022-02-04 3:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 15:24 [PATCH net-next] selftests: rtnetlink: Use more sensible tos values Guillaume Nault
2022-02-04 3: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=164394481045.31803.6913798555291608482.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=gnault@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
/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