From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@idosch.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
dsahern@gmail.com, yoshfuji@linux-ipv6.org, jiri@nvidia.com,
amcohen@nvidia.com, roopa@nvidia.com, bpoirier@nvidia.com,
sharpd@nvidia.com, mlxsw@nvidia.com, idosch@nvidia.com
Subject: Re: [PATCH net-next v2 00/10] Add notifications when route hardware flags change
Date: Wed, 03 Feb 2021 02:00:10 +0000 [thread overview]
Message-ID: <161231761084.3354.1009211825820091003.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210201194757.3463461-1-idosch@idosch.org>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Mon, 1 Feb 2021 21:47:47 +0200 you wrote:
> From: Ido Schimmel <idosch@nvidia.com>
>
> Routes installed to the kernel can be programmed to capable devices, in
> which case they are marked with one of two flags. RTM_F_OFFLOAD for
> routes that offload traffic from the kernel and RTM_F_TRAP for routes
> that trap packets to the kernel for processing (e.g., host routes).
>
> [...]
Here is the summary with links:
- [net-next,v2,01/10] netdevsim: fib: Convert the current occupancy to an atomic variable
https://git.kernel.org/netdev/net-next/c/9e635a21cae0
- [net-next,v2,02/10] netdevsim: fib: Perform the route programming in a non-atomic context
https://git.kernel.org/netdev/net-next/c/0ae3eb7b4611
- [net-next,v2,03/10] net: ipv4: Pass fib_rt_info as const to fib_dump_info()
https://git.kernel.org/netdev/net-next/c/085547891de5
- [net-next,v2,04/10] net: ipv4: Publish fib_nlmsg_size()
https://git.kernel.org/netdev/net-next/c/1e7bdec6bbc7
- [net-next,v2,05/10] net: ipv4: Emit notification when fib hardware flags are changed
https://git.kernel.org/netdev/net-next/c/680aea08e78c
- [net-next,v2,06/10] net: Pass 'net' struct as first argument to fib6_info_hw_flags_set()
https://git.kernel.org/netdev/net-next/c/fbaca8f895a6
- [net-next,v2,07/10] net: Do not call fib6_info_hw_flags_set() when IPv6 is disabled
https://git.kernel.org/netdev/net-next/c/efc42879ec9e
- [net-next,v2,08/10] net: ipv6: Emit notification when fib hardware flags are changed
https://git.kernel.org/netdev/net-next/c/907eea486888
- [net-next,v2,09/10] selftests: Extend fib tests to run with and without flags notifications
https://git.kernel.org/netdev/net-next/c/d1a7a489287c
- [net-next,v2,10/10] selftests: netdevsim: Add fib_notifications test
https://git.kernel.org/netdev/net-next/c/19d36d2971e6
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:[~2021-02-03 2:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 19:47 [PATCH net-next v2 00/10] Add notifications when route hardware flags change Ido Schimmel
2021-02-01 19:47 ` [PATCH net-next v2 01/10] netdevsim: fib: Convert the current occupancy to an atomic variable Ido Schimmel
2021-02-02 1:49 ` David Ahern
2021-02-01 19:47 ` [PATCH net-next v2 02/10] netdevsim: fib: Perform the route programming in a non-atomic context Ido Schimmel
2021-02-01 19:47 ` [PATCH net-next v2 03/10] net: ipv4: Pass fib_rt_info as const to fib_dump_info() Ido Schimmel
2021-02-01 19:47 ` [PATCH net-next v2 04/10] net: ipv4: Publish fib_nlmsg_size() Ido Schimmel
2021-02-01 19:47 ` [PATCH net-next v2 05/10] net: ipv4: Emit notification when fib hardware flags are changed Ido Schimmel
2021-02-01 19:47 ` [PATCH net-next v2 06/10] net: Pass 'net' struct as first argument to fib6_info_hw_flags_set() Ido Schimmel
2021-02-01 19:47 ` [PATCH net-next v2 07/10] net: Do not call fib6_info_hw_flags_set() when IPv6 is disabled Ido Schimmel
2021-02-01 19:47 ` [PATCH net-next v2 08/10] net: ipv6: Emit notification when fib hardware flags are changed Ido Schimmel
2021-02-01 19:47 ` [PATCH net-next v2 09/10] selftests: Extend fib tests to run with and without flags notifications Ido Schimmel
2021-02-01 19:47 ` [PATCH net-next v2 10/10] selftests: netdevsim: Add fib_notifications test Ido Schimmel
2021-02-03 2:00 ` 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=161231761084.3354.1009211825820091003.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=amcohen@nvidia.com \
--cc=bpoirier@nvidia.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=idosch@idosch.org \
--cc=idosch@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@nvidia.com \
--cc=sharpd@nvidia.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.