From: Ido Schimmel <idosch@nvidia.com>
To: Abdul Wasey <w453y.me@gmail.com>
Cc: netdev@vger.kernel.org, razor@blackwall.org, davem@davemloft.net,
edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, horatiu.vultur@microchip.com,
bridge@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/3] net: bridge: cfm: notify userspace on CFM config changes
Date: Wed, 7 Oct 2026 16:50:26 +0300 [thread overview]
Message-ID: <20261007135026.GA1066611@shredder> (raw)
In-Reply-To: <20261005043822.3106580-1-w453y.me@gmail.com>
On Mon, Oct 05, 2026 at 04:38:19AM +0000, Abdul Wasey wrote:
> CFM status changes are sent to userspace, config changes are not, so
> the only way to see a MEP being created, a peer added or CCM
> transmission started is to poll RTM_GETLINK. Patch 3 adds the
> notification. Patches 1 and 2 fix the two problems the AI review found
> in v1.
Given [1], I don't see a reason to review / apply this series. Will add
a deprecation warning to CFM and MRP.
[1] https://lore.kernel.org/netdev/20261006134441.3696739-1-w453y.me@gmail.com/
prev parent reply other threads:[~2026-10-07 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 4:38 [PATCH net-next v2 0/3] net: bridge: cfm: notify userspace on CFM config changes Abdul Wasey
2026-10-05 4:38 ` [PATCH net-next v2 1/3] net: bridge: cfm: count CFM config attributes in the link message size Abdul Wasey
2026-10-07 19:38 ` netdev-bot+sashiko
2026-10-05 4:38 ` [PATCH net-next v2 2/3] net: bridge: cfm: send an empty CFM nest when a bridge has no MEPs Abdul Wasey
2026-10-07 19:38 ` netdev-bot+sashiko
2026-10-05 4:38 ` [PATCH net-next v2 3/3] net: bridge: cfm: notify userspace on CFM config changes Abdul Wasey
2026-10-07 19:38 ` netdev-bot+sashiko
2026-10-07 13:50 ` Ido Schimmel [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=20261007135026.GA1066611@shredder \
--to=idosch@nvidia.com \
--cc=bridge@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horatiu.vultur@microchip.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.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 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.