From: Ido Schimmel <idosch@idosch.org>
To: Nikolay Aleksandrov <razor@blackwall.org>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
davem@davemloft.net, kuba@kernel.org, roopa@nvidia.com
Subject: Re: [Bridge] [PATCH net-next 3/6] net: bridge: fdb: add new nl attribute-based flush call
Date: Mon, 11 Apr 2022 11:41:12 +0300 [thread overview]
Message-ID: <YlPpqKFeAs5oCHGD@shredder> (raw)
In-Reply-To: <20220409105857.803667-4-razor@blackwall.org>
On Sat, Apr 09, 2022 at 01:58:54PM +0300, Nikolay Aleksandrov wrote:
> diff --git a/include/uapi/linux/if_bridge.h b/include/uapi/linux/if_bridge.h
> index 221a4256808f..2f3799cf14b2 100644
> --- a/include/uapi/linux/if_bridge.h
> +++ b/include/uapi/linux/if_bridge.h
> @@ -807,7 +807,15 @@ enum {
> /* embedded in IFLA_BRIDGE_FLUSH */
> enum {
> BRIDGE_FLUSH_UNSPEC,
> + BRIDGE_FLUSH_FDB,
> __BRIDGE_FLUSH_MAX
> };
> #define BRIDGE_FLUSH_MAX (__BRIDGE_FLUSH_MAX - 1)
> +
> +/* embedded in BRIDGE_FLUSH_FDB */
> +enum {
> + FDB_FLUSH_UNSPEC,
BTW, is there a reason this is not called FLUSH_FDB_UNSPEC given it's
embedded in BRIDGE_FLUSH_FDB, which is embedded in IFLA_BRIDGE_FLUSH ?
Regardless, in the cover letter you have '[ BRIDGE_FDB_FLUSH ]', which
is actually BRIDGE_FLUSH_FDB. I only noticed it because the code didn't
match what I had in my notebook, which I copied from the cover letter :)
> + __FDB_FLUSH_MAX
> +};
> +#define FDB_FLUSH_MAX (__FDB_FLUSH_MAX - 1)
> #endif /* _UAPI_LINUX_IF_BRIDGE_H */
WARNING: multiple messages have this Message-ID (diff)
From: Ido Schimmel <idosch@idosch.org>
To: Nikolay Aleksandrov <razor@blackwall.org>
Cc: netdev@vger.kernel.org, roopa@nvidia.com, kuba@kernel.org,
davem@davemloft.net, bridge@lists.linux-foundation.org
Subject: Re: [PATCH net-next 3/6] net: bridge: fdb: add new nl attribute-based flush call
Date: Mon, 11 Apr 2022 11:41:12 +0300 [thread overview]
Message-ID: <YlPpqKFeAs5oCHGD@shredder> (raw)
In-Reply-To: <20220409105857.803667-4-razor@blackwall.org>
On Sat, Apr 09, 2022 at 01:58:54PM +0300, Nikolay Aleksandrov wrote:
> diff --git a/include/uapi/linux/if_bridge.h b/include/uapi/linux/if_bridge.h
> index 221a4256808f..2f3799cf14b2 100644
> --- a/include/uapi/linux/if_bridge.h
> +++ b/include/uapi/linux/if_bridge.h
> @@ -807,7 +807,15 @@ enum {
> /* embedded in IFLA_BRIDGE_FLUSH */
> enum {
> BRIDGE_FLUSH_UNSPEC,
> + BRIDGE_FLUSH_FDB,
> __BRIDGE_FLUSH_MAX
> };
> #define BRIDGE_FLUSH_MAX (__BRIDGE_FLUSH_MAX - 1)
> +
> +/* embedded in BRIDGE_FLUSH_FDB */
> +enum {
> + FDB_FLUSH_UNSPEC,
BTW, is there a reason this is not called FLUSH_FDB_UNSPEC given it's
embedded in BRIDGE_FLUSH_FDB, which is embedded in IFLA_BRIDGE_FLUSH ?
Regardless, in the cover letter you have '[ BRIDGE_FDB_FLUSH ]', which
is actually BRIDGE_FLUSH_FDB. I only noticed it because the code didn't
match what I had in my notebook, which I copied from the cover letter :)
> + __FDB_FLUSH_MAX
> +};
> +#define FDB_FLUSH_MAX (__FDB_FLUSH_MAX - 1)
> #endif /* _UAPI_LINUX_IF_BRIDGE_H */
next prev parent reply other threads:[~2022-04-11 8:41 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 10:58 [Bridge] [PATCH net-next 0/6] net: bridge: add flush filtering support Nikolay Aleksandrov
2022-04-09 10:58 ` Nikolay Aleksandrov
2022-04-09 10:58 ` [Bridge] [PATCH net-next 1/6] net: bridge: add a generic flush operation Nikolay Aleksandrov
2022-04-09 10:58 ` Nikolay Aleksandrov
2022-04-09 10:58 ` [Bridge] [PATCH net-next 2/6] net: bridge: fdb: add support for fine-grained flushing Nikolay Aleksandrov
2022-04-09 10:58 ` Nikolay Aleksandrov
2022-04-11 8:20 ` [Bridge] " Ido Schimmel
2022-04-11 8:20 ` Ido Schimmel
2022-04-11 8:54 ` [Bridge] " Nikolay Aleksandrov
2022-04-11 8:54 ` Nikolay Aleksandrov
2022-04-09 10:58 ` [Bridge] [PATCH net-next 3/6] net: bridge: fdb: add new nl attribute-based flush call Nikolay Aleksandrov
2022-04-09 10:58 ` Nikolay Aleksandrov
2022-04-11 8:33 ` [Bridge] " Ido Schimmel
2022-04-11 8:33 ` Ido Schimmel
2022-04-11 9:01 ` [Bridge] " Nikolay Aleksandrov
2022-04-11 9:01 ` Nikolay Aleksandrov
2022-04-11 8:41 ` Ido Schimmel [this message]
2022-04-11 8:41 ` Ido Schimmel
2022-04-11 9:05 ` [Bridge] " Nikolay Aleksandrov
2022-04-11 9:05 ` Nikolay Aleksandrov
2022-04-09 10:58 ` [Bridge] [PATCH net-next 4/6] net: bridge: fdb: add support for flush filtering based on ndm flags and state Nikolay Aleksandrov
2022-04-09 10:58 ` Nikolay Aleksandrov
2022-04-11 8:47 ` [Bridge] " Ido Schimmel
2022-04-11 8:47 ` Ido Schimmel
2022-04-11 9:07 ` [Bridge] " Nikolay Aleksandrov
2022-04-11 9:07 ` Nikolay Aleksandrov
2022-04-09 10:58 ` [Bridge] [PATCH net-next 5/6] net: bridge: fdb: add support for flush filtering based on ifindex Nikolay Aleksandrov
2022-04-09 10:58 ` Nikolay Aleksandrov
2022-04-11 8:57 ` [Bridge] " Ido Schimmel
2022-04-11 8:57 ` Ido Schimmel
2022-04-11 9:03 ` [Bridge] " Nikolay Aleksandrov
2022-04-11 9:03 ` Nikolay Aleksandrov
2022-04-09 10:58 ` [Bridge] [PATCH net-next 6/6] net: bridge: fdb: add support for flush filtering based on vlan id Nikolay Aleksandrov
2022-04-09 10:58 ` Nikolay Aleksandrov
2022-04-09 12:36 ` [Bridge] [PATCH net-next 0/6] net: bridge: add flush filtering support Nikolay Aleksandrov
2022-04-09 12:36 ` Nikolay Aleksandrov
2022-04-10 20:43 ` [Bridge] " Nikolay Aleksandrov
2022-04-10 20:43 ` Nikolay Aleksandrov
2022-04-11 7:47 ` [Bridge] " Ido Schimmel
2022-04-11 7:47 ` Ido Schimmel
2022-04-11 8:53 ` [Bridge] " Nikolay Aleksandrov
2022-04-11 8:53 ` Nikolay Aleksandrov
2022-04-11 8:54 ` [Bridge] " Ido Schimmel
2022-04-11 8:54 ` Ido Schimmel
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=YlPpqKFeAs5oCHGD@shredder \
--to=idosch@idosch.org \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
--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 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.