From: Ido Schimmel <idosch@nvidia.com>
To: Abdul Wasey <w453y.me@gmail.com>
Cc: netdev@vger.kernel.org, dsahern@kernel.org,
stephen@networkplumber.org, razor@blackwall.org,
horatiu.vultur@microchip.com, bridge@lists.linux.dev
Subject: Re: [PATCH iproute2-next 0/2] bridge: add cfm command
Date: Tue, 6 Oct 2026 13:42:49 +0300 [thread overview]
Message-ID: <20261006104249.GA643161@shredder> (raw)
In-Reply-To: <20261004041307.2683990-1-w453y.me@gmail.com>
On Sun, Oct 04, 2026 at 04:13:05AM +0000, Abdul Wasey wrote:
> The bridge has had 802.1ag CFM support since 5.11, but iproute2 never
> got a command for it. The only userspace for it today is Microchip's out
> of tree cfm tool. This series adds "bridge cfm".
[...]
> 6 files changed, 1321 insertions(+), 3 deletions(-)
Please elaborate on the motivation: What is your interest in CFM? Are
you using it in production? Does anyone? Who needs this in iproute2?
What is missing from Microchip's cfm tool?
Looking at the kernel log, since CFM was merged six years ago, no new
features were added and the only bug fixes are for issues found by
static checkers and LLMs with no reviews from the original authors.
There are also no selftests.
If nobody cares about CFM or uses it, then I would prefer to start
deprecating it instead of accumulating more code that needs to be
maintained and that nobody is going to use.
next prev parent reply other threads:[~2026-10-06 10:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 4:13 [PATCH iproute2-next 0/2] bridge: add cfm command Abdul Wasey
2026-10-04 4:13 ` [PATCH iproute2-next 1/2] uapi: import cfm_bridge.h Abdul Wasey
2026-10-04 4:13 ` [PATCH iproute2-next 2/2] bridge: add cfm command Abdul Wasey
2026-10-06 10:42 ` Ido Schimmel [this message]
2026-10-06 13:44 ` [PATCH iproute2-next 0/2] " Abdul Wasey
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=20261006104249.GA643161@shredder \
--to=idosch@nvidia.com \
--cc=bridge@lists.linux.dev \
--cc=dsahern@kernel.org \
--cc=horatiu.vultur@microchip.com \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
--cc=stephen@networkplumber.org \
--cc=w453y.me@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