From: Jakub Kicinski <kuba@kernel.org>
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: Jay Vosburgh <jv@jvosburgh.net>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, Nikolay Aleksandrov <razor@blackwall.org>,
Simon Horman <horms@kernel.org>, Shuah Khan <shuah@kernel.org>,
Jonathan Corbet <corbet@lwn.net>, Petr Machata <petrm@nvidia.com>,
Amit Cohen <amcohen@nvidia.com>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Alessandro Zanni <alessandro.zanni87@gmail.com>,
linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 3/3] selftests: bonding: add test for LACP actor port priority
Date: Thu, 24 Jul 2025 07:35:01 -0700 [thread overview]
Message-ID: <20250724073501.1c0357c6@kernel.org> (raw)
In-Reply-To: <aIJDz3AgQtnzSR59@fedora>
On Thu, 24 Jul 2025 14:31:43 +0000 Hangbin Liu wrote:
> Should I drop this selftest as it needs the new iproute2 feature that has
> not applied yet?
No need, I'll add the iproute2 patch in the CI.
next prev parent reply other threads:[~2025-07-24 14:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 8:16 [PATCH net-next 0/3] bonding: support aggregator selection based on port priority Hangbin Liu
2025-07-24 8:16 ` [PATCH net-next 1/3] bonding: add support for per-port LACP actor priority Hangbin Liu
2025-07-25 8:55 ` Nikolay Aleksandrov
2025-08-12 4:48 ` Hangbin Liu
2025-07-24 8:16 ` [PATCH net-next 2/3] bonding: support aggregator selection based on port priority Hangbin Liu
2025-07-25 9:02 ` Nikolay Aleksandrov
2025-07-25 12:48 ` Hangbin Liu
2025-07-24 8:16 ` [PATCH net-next 3/3] selftests: bonding: add test for LACP actor " Hangbin Liu
2025-07-24 14:31 ` Hangbin Liu
2025-07-24 14:35 ` Jakub Kicinski [this message]
2025-07-25 2:20 ` Hangbin Liu
2025-07-25 14:27 ` Jakub Kicinski
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=20250724073501.1c0357c6@kernel.org \
--to=kuba@kernel.org \
--cc=alessandro.zanni87@gmail.com \
--cc=amcohen@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jv@jvosburgh.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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=razor@blackwall.org \
--cc=shuah@kernel.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 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.