From: Nikolay Aleksandrov via Bridge <bridge@lists.linux-foundation.org>
To: netdev@vger.kernel.org
Cc: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>,
roopa@cumulusnetworks.com, bridge@lists.linux-foundation.org,
davem@davemloft.net
Subject: [PATCH net-next 0/3] bridge: minor fdb cleanup
Date: Mon, 13 Feb 2017 14:59:08 +0100 [thread overview]
Message-ID: <1486994351-1137-1-git-send-email-nikolay@cumulusnetworks.com> (raw)
Hi,
These patches aim to simplify the bridge fdb API a little by removing some
redundant functions and converting them into wrappers of a single function.
Also add proper lock checking to avoid future mistakes for the search
functions.
Thanks,
Nik
Nikolay Aleksandrov (3):
bridge: fdb: converge fdb searching functions into one
bridge: fdb: add proper lock checks in searching functions
bridge: fdb: converge fdb_delete_by functions into one
net/bridge/br_device.c | 2 +-
net/bridge/br_fdb.c | 177 ++++++++++++++++++------------------------------
net/bridge/br_input.c | 4 +-
net/bridge/br_private.h | 14 +++-
4 files changed, 81 insertions(+), 116 deletions(-)
--
2.1.4
next reply other threads:[~2017-02-13 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 13:59 Nikolay Aleksandrov via Bridge [this message]
2017-02-13 13:59 ` [PATCH net-next 1/3] bridge: fdb: converge fdb searching functions into one Nikolay Aleksandrov
2017-02-13 13:59 ` [PATCH net-next 2/3] bridge: fdb: add proper lock checks in searching functions Nikolay Aleksandrov
2017-02-13 13:59 ` [PATCH net-next 3/3] bridge: fdb: converge fdb_delete_by functions into one Nikolay Aleksandrov
2017-02-14 17:41 ` [PATCH net-next 0/3] bridge: minor fdb 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=1486994351-1137-1-git-send-email-nikolay@cumulusnetworks.com \
--to=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.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 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).