public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@nvidia.com>
To: Petr Machata <petrm@nvidia.com>
Cc: netdev@vger.kernel.org, dsahern@gmail.com,
	stephen@networkplumber.org,
	Nikolay Aleksandrov <razor@blackwall.org>
Subject: Re: [PATCH iproute2-next 2/3] bridge: Add support for mcast_n_groups, mcast_max_groups
Date: Tue, 7 Feb 2023 09:39:22 +0200	[thread overview]
Message-ID: <Y+IAKgXSFtJvERWt@shredder> (raw)
In-Reply-To: <82cb1211d85e02e6247cb9a141aad68027cbefac.1675705077.git.petrm@nvidia.com>

On Mon, Feb 06, 2023 at 06:50:26PM +0100, Petr Machata wrote:
> A total of four new bridge attributes are being added to the kernel:
> mcast_n_groups and mcast_max_groups, as link and vlan attributes. Add
> to the bridge tool the support code to enable setting and querying
> these attributes. Example usage:

[...]

> 
> Signed-off-by: Petr Machata <petrm@nvidia.com>

Reviewed-by: Ido Schimmel <idosch@nvidia.com>

  reply	other threads:[~2023-02-07  7:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06 17:50 [PATCH iproute2-next 0/3] bridge: Support mcast_n_groups, mcast_max_groups Petr Machata
2023-02-06 17:50 ` [PATCH iproute2-next 1/3] uapi: Update if_bridge, if_link Petr Machata
2023-02-06 17:50 ` [PATCH iproute2-next 2/3] bridge: Add support for mcast_n_groups, mcast_max_groups Petr Machata
2023-02-07  7:39   ` Ido Schimmel [this message]
2023-02-06 17:50 ` [PATCH iproute2-next 3/3] man: man8: bridge: Describe mcast_max_groups Petr Machata
2023-02-06 23:08   ` Nikolay Aleksandrov
2023-02-07  9:49     ` Petr Machata
2023-02-07  7:50   ` 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=Y+IAKgXSFtJvERWt@shredder \
    --to=idosch@nvidia.com \
    --cc=dsahern@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=petrm@nvidia.com \
    --cc=razor@blackwall.org \
    --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