From: Ido Schimmel <idosch@idosch.org>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, dsahern@gmail.com,
mlxsw@nvidia.com, Ido Schimmel <idosch@nvidia.com>
Subject: [PATCH net-next 0/5] nexthop: Small changes
Date: Tue, 15 Sep 2020 14:40:58 +0300 [thread overview]
Message-ID: <20200915114103.88883-1-idosch@idosch.org> (raw)
From: Ido Schimmel <idosch@nvidia.com>
This patch set contains a few small changes that I split out of the RFC
I sent last week [1]. Main change is the conversion of the nexthop
notification chain to a blocking chain so that it could be reused by
device drivers for nexthop objects programming in the future.
Tested with fib_nexthops.sh:
Tests passed: 164
Tests failed: 0
[1] https://lore.kernel.org/netdev/20200908091037.2709823-1-idosch@idosch.org/
Ido Schimmel (5):
nexthop: Remove unused function declaration from header file
nexthop: Remove NEXTHOP_EVENT_ADD
nexthop: Convert to blocking notification chain
nexthop: Only emit a notification when nexthop is actually deleted
selftests: fib_nexthops: Test cleanup of FDB entries following nexthop
deletion
include/net/netns/nexthop.h | 2 +-
include/net/nexthop.h | 4 ----
net/ipv4/nexthop.c | 17 +++++++++--------
tools/testing/selftests/net/fib_nexthops.sh | 14 ++++++++++++++
4 files changed, 24 insertions(+), 13 deletions(-)
--
2.26.2
next reply other threads:[~2020-09-16 0:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 11:40 Ido Schimmel [this message]
2020-09-15 11:40 ` [PATCH net-next 1/5] nexthop: Remove unused function declaration from header file Ido Schimmel
2020-09-15 11:41 ` [PATCH net-next 2/5] nexthop: Remove NEXTHOP_EVENT_ADD Ido Schimmel
2020-09-15 11:41 ` [PATCH net-next 3/5] nexthop: Convert to blocking notification chain Ido Schimmel
2020-09-15 11:41 ` [PATCH net-next 4/5] nexthop: Only emit a notification when nexthop is actually deleted Ido Schimmel
2020-09-15 11:41 ` [PATCH net-next 5/5] selftests: fib_nexthops: Test cleanup of FDB entries following nexthop deletion Ido Schimmel
2020-09-15 23:32 ` [PATCH net-next 0/5] nexthop: Small changes David Miller
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=20200915114103.88883-1-idosch@idosch.org \
--to=idosch@idosch.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.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.