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, roopa@nvidia.com, sharpd@nvidia.com,
mlxsw@nvidia.com, idosch@nvidia.com
Subject: Re: [PATCH net 0/2] nexthop: Do not flush blackhole nexthops when loopback goes down
Date: Thu, 04 Mar 2021 22:20:07 +0000 [thread overview]
Message-ID: <161489640724.7668.480896092445569577.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210304085754.1929848-1-idosch@idosch.org>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Thu, 4 Mar 2021 10:57:52 +0200 you wrote:
> From: Ido Schimmel <idosch@nvidia.com>
>
> Patch #1 prevents blackhole nexthops from being flushed when the
> loopback device goes down given that as far as user space is concerned,
> these nexthops do not have a nexthop device.
>
> Patch #2 adds a test case.
>
> [...]
Here is the summary with links:
- [net,1/2] nexthop: Do not flush blackhole nexthops when loopback goes down
https://git.kernel.org/netdev/net/c/76c03bf8e262
- [net,2/2] selftests: fib_nexthops: Test blackhole nexthops when loopback goes down
https://git.kernel.org/netdev/net/c/3a1099d3147f
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-03-04 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 8:57 [PATCH net 0/2] nexthop: Do not flush blackhole nexthops when loopback goes down Ido Schimmel
2021-03-04 8:57 ` [PATCH net 1/2] " Ido Schimmel
2021-03-04 8:57 ` [PATCH net 2/2] selftests: fib_nexthops: Test " Ido Schimmel
2021-03-04 22: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=161489640724.7668.480896092445569577.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=idosch@idosch.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@nvidia.com \
--cc=sharpd@nvidia.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 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.