From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
To: netdev@vger.kernel.org
Cc: roopa@cumulusnetworks.com, dwalton@cumulusnetworks.com,
stephen@networkplumber.org, davem@davemloft.net,
Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Subject: [PATCH net-next 0/4] bridge: add support for PIM hello router ports
Date: Mon, 31 Oct 2016 13:21:01 +0100 [thread overview]
Message-ID: <1477916465-20406-1-git-send-email-nikolay@cumulusnetworks.com> (raw)
Hi,
The first 3 patches of this set do minor cleanups and add some helpers to
the PIM header file. Patch 4 adds a way to detect mcast router ports via
PIM hello messages, they're marked as temporary and are not considered for
querier. There's more detailed information in patch 4's commit message.
Thanks,
Nik
Nikolay Aleksandrov (4):
net: pim: add common pimhdr struct and helpers
net: pim: add a helper to check for IPv4 all pim routers address
net: pim: add all RFC7761 message types
bridge: mcast: add router port on PIM hello message
include/linux/pim.h | 81 +++++++++++++++++++++++++++++++++++++++++------
net/bridge/br_multicast.c | 22 ++++++++++++-
net/ipv4/ipmr.c | 2 +-
net/ipv6/ip6mr.c | 2 +-
4 files changed, 95 insertions(+), 12 deletions(-)
--
2.1.4
next reply other threads:[~2016-10-31 12:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 12:21 Nikolay Aleksandrov [this message]
2016-10-31 12:21 ` [PATCH net-next 1/4] net: pim: add common pimhdr struct and helpers Nikolay Aleksandrov
2016-10-31 12:21 ` [PATCH net-next 2/4] net: pim: add a helper to check for IPv4 all pim routers address Nikolay Aleksandrov
2016-10-31 12:21 ` [PATCH net-next 3/4] net: pim: add all RFC7761 message types Nikolay Aleksandrov
2016-10-31 12:21 ` [PATCH net-next 4/4] bridge: mcast: add router port on PIM hello message Nikolay Aleksandrov
2016-10-31 20:18 ` [PATCH net-next 0/4] bridge: add support for PIM hello router ports 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=1477916465-20406-1-git-send-email-nikolay@cumulusnetworks.com \
--to=nikolay@cumulusnetworks.com \
--cc=davem@davemloft.net \
--cc=dwalton@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=stephen@networkplumber.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).