From: Guenter Roeck <linux@roeck-us.net>
To: "Linus Lüssing" <linus.luessing@c0d3.blue>
Cc: netdev@vger.kernel.org, Roopa Prabhu <roopa@nvidia.com>,
Nikolay Aleksandrov <nikolay@nvidia.com>,
Jakub Kicinski <kuba@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
bridge@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [net-next v4 05/11] net: bridge: mcast: prepare is-router function for mcast router split
Date: Sat, 15 May 2021 09:44:57 -0700 [thread overview]
Message-ID: <20210515164457.GA1387203@roeck-us.net> (raw)
In-Reply-To: <20210513132053.23445-6-linus.luessing@c0d3.blue>
On Thu, May 13, 2021 at 03:20:47PM +0200, Linus Lüssing wrote:
> In preparation for the upcoming split of multicast router state into
> their IPv4 and IPv6 variants make br_multicast_is_router() protocol
> family aware.
>
> Note that for now br_ip6_multicast_is_router() uses the currently still
> common ip4_mc_router_timer for now. It will be renamed to
> ip6_mc_router_timer later when the split is performed.
>
> While at it also renames the "1" and "2" constants in
> br_multicast_is_router() to the MDB_RTR_TYPE_TEMP_QUERY and
> MDB_RTR_TYPE_PERM enums.
>
> Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue>
Just in case this hasn't been reported yet. In next-20210514:
$ git grep br_multicast_is_router
net/bridge/br_input.c: br_multicast_is_router(br, skb)) {
net/bridge/br_multicast.c: is_router = br_multicast_is_router(br, NULL);
net/bridge/br_private.h:br_multicast_is_router(struct net_bridge *br, struct sk_buff *skb)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
net/bridge/br_private.h:static inline bool br_multicast_is_router(struct net_bridge *br)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Guenter
next prev parent reply other threads:[~2021-05-15 16:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 13:20 [PATCH net-next v4 00/11] net: bridge: split IPv4/v6 mc router state and export for batman-adv Linus Lüssing
2021-05-13 13:20 ` [net-next v4 01/11] net: bridge: mcast: rename multicast router lists and timers Linus Lüssing
2021-05-13 13:20 ` [net-next v4 02/11] net: bridge: mcast: add wrappers for router node retrieval Linus Lüssing
2021-05-13 13:20 ` [net-next v4 03/11] net: bridge: mcast: prepare mdb netlink for mcast router split Linus Lüssing
2021-05-13 13:20 ` [net-next v4 04/11] net: bridge: mcast: prepare query reception " Linus Lüssing
2021-05-13 13:20 ` [net-next v4 05/11] net: bridge: mcast: prepare is-router function " Linus Lüssing
2021-05-15 16:44 ` Guenter Roeck [this message]
2021-05-13 13:20 ` [net-next v4 06/11] net: bridge: mcast: prepare expiry functions " Linus Lüssing
2021-05-13 13:20 ` [net-next v4 07/11] net: bridge: mcast: prepare add-router function " Linus Lüssing
2021-05-13 13:20 ` [net-next v4 08/11] net: bridge: mcast: split router port del+notify " Linus Lüssing
2021-05-13 13:20 ` [net-next v4 09/11] net: bridge: mcast: split multicast router state for IPv4 and IPv6 Linus Lüssing
2021-05-13 13:20 ` [net-next v4 10/11] net: bridge: mcast: add ip4+ip6 mcast router timers to mdb netlink Linus Lüssing
2021-05-13 13:20 ` [net-next v4 11/11] net: bridge: mcast: export multicast router presence adjacent to a port Linus Lüssing
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=20210515164457.GA1387203@roeck-us.net \
--to=linux@roeck-us.net \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linus.luessing@c0d3.blue \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=roopa@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 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).