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,
idosch@nvidia.com
Subject: Re: [PATCH net-next 0/4] ipv4: Prepare core ipv4 files to future .flowi4_tos conversion.
Date: Tue, 29 Oct 2024 18:50:44 +0000 [thread overview]
Message-ID: <173022784423.787364.13867431167954708409.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1729530028.git.gnault@redhat.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 22 Oct 2024 11:47:52 +0200 you wrote:
> Continue preparing users of ->flowi4_tos (struct flowi4) to the future
> conversion of this field (from __u8 to dscp_t). The objective is to
> have type annotation to properly separate DSCP bits from ECN ones. This
> way we'll ensure that ECN doesn't interfere with DSCP and avoid
> regressions where it break routing descisions (fib rules in particular).
>
> This series concentrates on some easy IPv4 conversions where
> ->flowi4_tos is set directly from an IPv4 header, so we can get the
> DSCP value using the ip4h_dscp() helper function.
>
> [...]
Here is the summary with links:
- [net-next,1/4] ipv4: Prepare fib_compute_spec_dst() to future .flowi4_tos conversion.
https://git.kernel.org/netdev/net-next/c/b76ebf22c578
- [net-next,2/4] ipv4: Prepare icmp_reply() to future .flowi4_tos conversion.
https://git.kernel.org/netdev/net-next/c/0ed373390c5c
- [net-next,3/4] ipv4: Prepare ipmr_rt_fib_lookup() to future .flowi4_tos conversion.
https://git.kernel.org/netdev/net-next/c/6ab04392dd08
- [net-next,4/4] ipv4: Prepare ip_rt_get_source() to future .flowi4_tos conversion.
https://git.kernel.org/netdev/net-next/c/85ef52e8693c
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-10-29 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 9:47 [PATCH net-next 0/4] ipv4: Prepare core ipv4 files to future .flowi4_tos conversion Guillaume Nault
2024-10-22 9:48 ` [PATCH net-next 1/4] ipv4: Prepare fib_compute_spec_dst() " Guillaume Nault
2024-10-22 12:35 ` Ido Schimmel
2024-10-22 9:48 ` [PATCH net-next 2/4] ipv4: Prepare icmp_reply() " Guillaume Nault
2024-10-22 12:36 ` Ido Schimmel
2024-10-22 9:48 ` [PATCH net-next 3/4] ipv4: Prepare ipmr_rt_fib_lookup() " Guillaume Nault
2024-10-22 12:37 ` Ido Schimmel
2024-10-22 9:48 ` [PATCH net-next 4/4] ipv4: Prepare ip_rt_get_source() " Guillaume Nault
2024-10-22 12:37 ` Ido Schimmel
2024-10-29 18:50 ` 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=173022784423.787364.13867431167954708409.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=idosch@nvidia.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).