From: Nikolay Aleksandrov <razor@blackwall.org>
To: Joseph Huang <Joseph.Huang@garmin.com>, netdev@vger.kernel.org
Cc: Joseph Huang <joseph.huang.2024@gmail.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Roopa Prabhu <roopa@nvidia.com>, Simon Horman <horms@kernel.org>,
linux-kernel@vger.kernel.org, bridge@lists.linux.dev
Subject: Re: [Patch v5 net-next 1/3] net: bridge: mcast: Add offload failed mdb flag
Date: Fri, 11 Apr 2025 18:41:02 +0300 [thread overview]
Message-ID: <7e7746f3-3113-4f80-b9e1-71d28048c2d3@blackwall.org> (raw)
In-Reply-To: <20250411150323.1117797-2-Joseph.Huang@garmin.com>
On 4/11/25 18:03, Joseph Huang wrote:
> Add MDB_FLAGS_OFFLOAD_FAILED and MDB_PG_FLAGS_OFFLOAD_FAILED to indicate
> that an attempt to offload the MDB entry to switchdev has failed.
>
> Signed-off-by: Joseph Huang <Joseph.Huang@garmin.com>
> ---
> include/uapi/linux/if_bridge.h | 9 +++++----
> net/bridge/br_mdb.c | 2 ++
> net/bridge/br_private.h | 20 +++++++++++++++-----
> net/bridge/br_switchdev.c | 9 +++++----
> 4 files changed, 27 insertions(+), 13 deletions(-)
>
Acked-by: Nikolay Aleksandrov <razor@blackwall.org>
next prev parent reply other threads:[~2025-04-11 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 15:03 [Patch v5 net-next 0/3] Add support for mdb offload failure notification Joseph Huang
2025-04-11 15:03 ` [Patch v5 net-next 1/3] net: bridge: mcast: Add offload failed mdb flag Joseph Huang
2025-04-11 15:41 ` Nikolay Aleksandrov [this message]
2025-04-11 15:03 ` [Patch v5 net-next 2/3] net: bridge: Add offload_fail_notification bopt Joseph Huang
2025-04-11 15:03 ` [Patch v5 net-next 3/3] net: bridge: mcast: Notify on mdb offload failure Joseph Huang
2025-04-14 23:10 ` [Patch v5 net-next 0/3] Add support for mdb offload failure notification patchwork-bot+netdevbpf
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=7e7746f3-3113-4f80-b9e1-71d28048c2d3@blackwall.org \
--to=razor@blackwall.org \
--cc=Joseph.Huang@garmin.com \
--cc=andrew+netdev@lunn.ch \
--cc=bridge@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=joseph.huang.2024@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®