Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org, jv@jvosburgh.net, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, shuah@kernel.org,
	corbet@lwn.net, petrm@nvidia.com, amcohen@nvidia.com,
	vladimir.oltean@nxp.com, stephen@networkplumber.org,
	dsahern@gmail.com, jonas.gorski@gmail.com,
	linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCHv5 net-next 0/3] bonding: support aggregator selection based on port priority
Date: Tue, 09 Sep 2025 09:20:09 +0000	[thread overview]
Message-ID: <175740960963.593749.1942861170014079998.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250902064501.360822-1-liuhangbin@gmail.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Tue,  2 Sep 2025 06:44:58 +0000 you wrote:
> This patchset introduces a new per-port bonding option: `ad_actor_port_prio`.
> 
> It allows users to configure the actor's port priority, which can then be used
> by the bonding driver for aggregator selection based on port priority.
> 
> This provides finer control over LACP aggregator choice, especially in setups
> with multiple eligible aggregators over 2 switches.
> 
> [...]

Here is the summary with links:
  - [PATCHv5,net-next,1/3] bonding: add support for per-port LACP actor priority
    https://git.kernel.org/netdev/net-next/c/6b6dc81ee7e8
  - [PATCHv5,net-next,2/3] bonding: support aggregator selection based on port priority
    https://git.kernel.org/netdev/net-next/c/e5a6643435fa
  - [PATCHv5,net-next,3/3] selftests: bonding: add test for LACP actor port priority
    https://git.kernel.org/netdev/net-next/c/c2377f1763e9

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-09-09  9:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-02  6:44 [PATCHv5 net-next 0/3] bonding: support aggregator selection based on port priority Hangbin Liu
2025-09-02  6:44 ` [PATCHv5 net-next 1/3] bonding: add support for per-port LACP actor priority Hangbin Liu
2025-09-02  6:45 ` [PATCHv5 net-next 2/3] bonding: support aggregator selection based on port priority Hangbin Liu
2025-09-02  6:45 ` [PATCHv5 net-next 3/3] selftests: bonding: add test for LACP actor " Hangbin Liu
2025-09-09  9:20 ` 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=175740960963.593749.1942861170014079998.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=amcohen@nvidia.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jonas.gorski@gmail.com \
    --cc=jv@jvosburgh.net \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=liuhangbin@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petrm@nvidia.com \
    --cc=shuah@kernel.org \
    --cc=stephen@networkplumber.org \
    --cc=vladimir.oltean@nxp.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