From: Hangbin Liu <liuhangbin@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: Jakub Kicinski <kuba@kernel.org>, Jay Vosburgh <jv@jvosburgh.net>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
Simon Horman <horms@kernel.org>,
Mahesh Bandewar <maheshb@google.com>,
Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCHv2 net-next 0/3] bonding: fix 802.3ad churn machine and port state issues
Date: Thu, 26 Feb 2026 12:40:13 +0000 [thread overview]
Message-ID: <aaA_Lb4cAAmp-w9q@fedora> (raw)
In-Reply-To: <4f497c2f-d086-46ae-bad7-44285bc34a2a@redhat.com>
On Thu, Feb 26, 2026 at 12:55:48PM +0100, Paolo Abeni wrote:
> On 2/23/26 2:55 AM, Hangbin Liu wrote:
> > I'm not sure what I should do for this patch set. Should I re-post to net-next or net?
>
> Jakub and me discussed the topic off-list and the current agreement is
> repost for 'net', with fixes tag.
Thanks, I will repost to net.
Regards
Hangbin
prev parent reply other threads:[~2026-02-26 12:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 6:49 [PATCHv2 net-next 0/3] bonding: fix 802.3ad churn machine and port state issues Hangbin Liu
2026-01-14 6:49 ` [PATCHv2 net-next 1/3] bonding: set AD_RX_PORT_DISABLED when disabling a port Hangbin Liu
2026-01-14 6:49 ` [PATCHv2 net-next 2/3] bonding: restructure ad_churn_machine Hangbin Liu
2026-01-19 20:22 ` Jakub Kicinski
2026-01-20 5:51 ` Hangbin Liu
2026-01-20 8:29 ` Paolo Abeni
2026-01-20 23:11 ` Jakub Kicinski
2026-01-21 7:58 ` Paolo Abeni
2026-01-22 1:10 ` Jakub Kicinski
2026-01-14 6:49 ` [PATCHv2 net-next 3/3] selftests: bonding: add mux and churn state testing Hangbin Liu
2026-02-02 1:14 ` [PATCHv2 net-next 0/3] bonding: fix 802.3ad churn machine and port state issues Hangbin Liu
2026-02-02 9:27 ` Paolo Abeni
2026-02-23 1:55 ` Hangbin Liu
2026-02-26 11:55 ` Paolo Abeni
2026-02-26 12:40 ` Hangbin Liu [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=aaA_Lb4cAAmp-w9q@fedora \
--to=liuhangbin@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jv@jvosburgh.net \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maheshb@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.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.