From: patchwork-bot+netdevbpf@kernel.org
To: Guillaume Nault <gnault@redhat.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, tchornyi@marvell.com, idosch@nvidia.com,
petrm@nvidia.com, yoshfuji@linux-ipv6.org, dsahern@kernel.org
Subject: Re: [PATCH net-next 0/5] ipv4: Convert several tos fields to dscp_t
Date: Tue, 12 Apr 2022 01:20:15 +0000 [thread overview]
Message-ID: <164972641536.27669.11150630095148243278.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1649445279.git.gnault@redhat.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 8 Apr 2022 22:08:34 +0200 you wrote:
> Continue the work started with commit a410a0cf9885 ("ipv6: Define
> dscp_t and stop taking ECN bits into account in fib6-rules") and
> convert more structure fields and variables to dscp_t. This series
> focuses on struct fib_rt_info, struct fib_entry_notifier_info and their
> users (networking drivers).
>
> The purpose of dscp_t is to ensure that ECN bits don't influence IP
> route lookups. It does so by ensuring that dscp_t variables have the
> ECN bits cleared.
>
> [...]
Here is the summary with links:
- [net-next,1/5] ipv4: Use dscp_t in struct fib_rt_info
https://git.kernel.org/netdev/net-next/c/888ade8f90d7
- [net-next,2/5] ipv4: Use dscp_t in struct fib_entry_notifier_info
https://git.kernel.org/netdev/net-next/c/568a3f33b427
- [net-next,3/5] netdevsim: Use dscp_t in struct nsim_fib4_rt
https://git.kernel.org/netdev/net-next/c/20bbf32efe1e
- [net-next,4/5] mlxsw: Use dscp_t in struct mlxsw_sp_fib4_entry
https://git.kernel.org/netdev/net-next/c/046eabbf1991
- [net-next,5/5] net: marvell: prestera: Use dscp_t in struct prestera_kern_fib_cache
https://git.kernel.org/netdev/net-next/c/9f6982e9a3c2
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-04-12 1:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 20:08 [PATCH net-next 0/5] ipv4: Convert several tos fields to dscp_t Guillaume Nault
2022-04-08 20:08 ` [PATCH net-next 1/5] ipv4: Use dscp_t in struct fib_rt_info Guillaume Nault
2022-04-10 17:01 ` Ido Schimmel
2022-04-10 17:58 ` David Ahern
2022-04-08 20:08 ` [PATCH net-next 2/5] ipv4: Use dscp_t in struct fib_entry_notifier_info Guillaume Nault
2022-04-10 17:01 ` Ido Schimmel
2022-04-10 17:59 ` David Ahern
2022-04-08 20:08 ` [PATCH net-next 3/5] netdevsim: Use dscp_t in struct nsim_fib4_rt Guillaume Nault
2022-04-09 3:38 ` Jakub Kicinski
2022-04-10 17:02 ` Ido Schimmel
2022-04-10 18:00 ` David Ahern
2022-04-08 20:08 ` [PATCH net-next 4/5] mlxsw: Use dscp_t in struct mlxsw_sp_fib4_entry Guillaume Nault
2022-04-10 17:02 ` Ido Schimmel
2022-04-08 20:08 ` [PATCH net-next 5/5] net: marvell: prestera: Use dscp_t in struct prestera_kern_fib_cache Guillaume Nault
2022-04-11 15:09 ` Yevhen Orlov
2022-04-12 1: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=164972641536.27669.11150630095148243278.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=gnault@redhat.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=tchornyi@marvell.com \
--cc=yoshfuji@linux-ipv6.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 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.