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 <ido...@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


Reply via email to