From: Stephen Hemminger <stephen@networkplumber.org>
To: Vivien Didelot <vivien.didelot@gmail.com>
Cc: netdev@vger.kernel.org, Russell King <linux@armlinux.org.uk>
Subject: Re: [PATCH iproute2 v2] bridge: make mcast_flood description consistent
Date: Thu, 21 Feb 2019 14:48:38 -0800 [thread overview]
Message-ID: <20190221144838.2005f922@shemminger-XPS-13-9360> (raw)
In-Reply-To: <20190220163357.25968-1-vivien.didelot@gmail.com>
On Wed, 20 Feb 2019 11:33:57 -0500
Vivien Didelot <vivien.didelot@gmail.com> wrote:
> This patch simply changes the description of the mcast_flood flag
> with "flood" instead of "be flooded with" to avoid confusion, and be
> consistent with the description of the flooding flag, which "Controls
> whether a given port will *flood* unicast traffic for which there is
> no FDB entry."
>
> At the same time, fix the documentation for the "flood" flag which
> is incorrectly described as "flooding on" or "flooding off".
>
> Signed-off-by: Vivien Didelot <vivien.didelot@gmail.com>
Applied
prev parent reply other threads:[~2019-02-21 22:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 16:33 [PATCH iproute2 v2] bridge: make mcast_flood description consistent Vivien Didelot
2019-02-21 22:48 ` Stephen Hemminger [this message]
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=20190221144838.2005f922@shemminger-XPS-13-9360 \
--to=stephen@networkplumber.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.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