From: Jakub Kicinski <kuba@kernel.org>
To: Joseph Huang <Joseph.Huang@garmin.com>
Cc: <netdev@vger.kernel.org>,
Joseph Huang <joseph.huang.2024@gmail.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Roopa Prabhu <roopa@nvidia.com>,
Nikolay Aleksandrov <razor@blackwall.org>,
Simon Horman <horms@kernel.org>, <linux-kernel@vger.kernel.org>,
<bridge@lists.linux.dev>
Subject: Re: [Patch v3 net-next 0/3] Add support for mdb offload failure notification
Date: Mon, 7 Apr 2025 10:29:41 -0700 [thread overview]
Message-ID: <20250407102941.4331a41e@kernel.org> (raw)
In-Reply-To: <20250404212940.1837879-1-Joseph.Huang@garmin.com>
On Fri, 4 Apr 2025 17:29:32 -0400 Joseph Huang wrote:
> Currently the bridge does not provide real-time feedback to user space
> on whether or not an attempt to offload an mdb entry was successful.
>
> This patch set adds support to notify user space about failed offload
> attempts, and is controlled by a new knob mdb_offload_fail_notification.
>
> A break-down of the patches in the series:
>
> Patch 1 adds offload failed flag to indicate that the offload attempt
> has failed. The flag is reflected in netlink mdb entry flags.
>
> Patch 2 adds the new bridge bool option mdb_offload_fail_notification.
>
> Patch 3 notifies user space when the result is known, controlled by
> mdb_offload_fail_notification setting.
You submitted this during the merge window, when the net-next tree
was closed. See:
https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
Could you repost so that the series will be re-enqueued?
Thanks!
--
pw-bot: defer
next prev parent reply other threads:[~2025-04-07 17:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 21:29 [Patch v3 net-next 0/3] Add support for mdb offload failure notification Joseph Huang
2025-04-04 21:29 ` [Patch v3 net-next 1/3] net: bridge: mcast: Add offload failed mdb flag Joseph Huang
2025-04-05 8:09 ` Nikolay Aleksandrov
2025-04-04 21:29 ` [Patch v3 net-next 2/3] net: bridge: Add offload_fail_notification bopt Joseph Huang
2025-04-04 21:29 ` [Patch v3 net-next 3/3] net: bridge: mcast: Notify on mdb offload failure Joseph Huang
2025-04-05 8:10 ` Nikolay Aleksandrov
2025-04-07 17:29 ` Jakub Kicinski [this message]
2025-04-07 18:15 ` [Patch v3 net-next 0/3] Add support for mdb offload failure notification Joseph Huang
2025-04-07 18:37 ` Jakub Kicinski
2025-04-07 18:40 ` Joseph Huang
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=20250407102941.4331a41e@kernel.org \
--to=kuba@kernel.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=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--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;
as well as URLs for NNTP newsgroup(s).