From: patchwork-bot+netdevbpf@kernel.org
To: Louis Scalbert <louis.scalbert@6wind.com>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch, jv@jvosburgh.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
fbl@redhat.com, andy@greyhouse.net, shemminger@vyatta.com,
maheshb@google.com, jonas.gorski@gmail.com, horms@kernel.org,
stephen@networkplumber.org, matttbe@kernel.org,
dsahern@kernel.org
Subject: Re: [PATCH iproute2-next v6] ip/bond: add lacp_strict support
Date: Fri, 21 Aug 2026 21:30:12 +0000 [thread overview]
Message-ID: <178734781256.1491177.16610625029555097734.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260820164352.1933916-1-louis.scalbert@6wind.com>
Hello:
This patch was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Thu, 20 Aug 2026 18:43:52 +0200 you wrote:
> lacp_strict defines the behavior of a LACP bonding interface
> when no slaves are in Collecting_Distributing state while at least
> 'min_links' slaves have carrier.
>
> In the default (off) mode, the bonding master remains up and a
> single slave is selected for TX/RX, while traffic received on other
> slaves is dropped. This preserves the existing behavior.
>
> [...]
Here is the summary with links:
- [iproute2-next,v6] ip/bond: add lacp_strict support
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=30365d0967bd
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-21 21:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 16:43 [PATCH iproute2-next v6] ip/bond: add lacp_strict support Louis Scalbert
2026-08-21 21:30 ` patchwork-bot+netdevbpf [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=178734781256.1491177.16610625029555097734.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andy@greyhouse.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fbl@redhat.com \
--cc=horms@kernel.org \
--cc=jonas.gorski@gmail.com \
--cc=jv@jvosburgh.net \
--cc=kuba@kernel.org \
--cc=louis.scalbert@6wind.com \
--cc=maheshb@google.com \
--cc=matttbe@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shemminger@vyatta.com \
--cc=stephen@networkplumber.org \
/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.