From: Jiri Pirko <jiri@resnulli.us>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, idosch@mellanox.com, mlxsw@mellanox.com,
ivecera@redhat.com, kuznet@ms2.inr.ac.ru, jmorris@namei.org,
yoshfuji@linux-ipv6.org, kaber@trash.net
Subject: [patch net-next 0/2] ipv4: fib: FIB notifications cleanup
Date: Fri, 10 Mar 2017 08:56:17 +0100 [thread overview]
Message-ID: <1489132579-12664-1-git-send-email-jiri@resnulli.us> (raw)
From: Jiri Pirko <jiri@mellanox.com>
Ido says:
The first patch moves the core FIB notification code to a separate file,
so that code related to FIB rules is placed in fib_rules.c and not
fib_trie.c. The reason for the change will become even more apparent in
follow-up patchset where we extend the FIB rules notifications.
Second patch removes a redundant argument.
Ido Schimmel (2):
ipv4: fib: Move FIB notification code to a separate file
ipv4: fib: Remove redundant argument
include/net/ip_fib.h | 12 ++++++
net/ipv4/Makefile | 2 +-
net/ipv4/fib_notifier.c | 86 ++++++++++++++++++++++++++++++++++++++
net/ipv4/fib_rules.c | 8 ++++
net/ipv4/fib_trie.c | 108 +++---------------------------------------------
5 files changed, 113 insertions(+), 103 deletions(-)
create mode 100644 net/ipv4/fib_notifier.c
--
2.7.4
next reply other threads:[~2017-03-10 7:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 7:56 Jiri Pirko [this message]
2017-03-10 7:56 ` [patch net-next 1/2] ipv4: fib: Move FIB notification code to a separate file Jiri Pirko
2017-03-10 16:31 ` David Ahern
2017-03-10 7:56 ` [patch net-next 2/2] ipv4: fib: Remove redundant argument Jiri Pirko
2017-03-10 16:31 ` David Ahern
2017-03-10 17:45 ` [patch net-next 0/2] ipv4: fib: FIB notifications cleanup 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=1489132579-12664-1-git-send-email-jiri@resnulli.us \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=idosch@mellanox.com \
--cc=ivecera@redhat.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).