From: patchwork-bot+netdevbpf@kernel.org
To: Jonathan Toppins <jtoppins@redhat.com>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, j.vosburgh@gmail.com
Subject: Re: [PATCH net-next v2 0/2] bonding: fix bond recovery in mode 2
Date: Thu, 24 Nov 2022 04:20:16 +0000 [thread overview]
Message-ID: <166926361627.22792.14683635371904949142.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1669147951.git.jtoppins@redhat.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 22 Nov 2022 15:25:03 -0500 you wrote:
> When a bond is configured with a non-zero updelay and in mode 2 the bond
> never recovers after all slaves lose link. The first patch adds
> selftests that demonstrate the issue and the second patch fixes the
> issue by ignoring the updelay when there are no usable slaves.
>
> v2:
> * repost to net tree, suggested by Paolo Abeni
> * reduce number of icmp echos used in test, suggested by Paolo Abeni
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] selftests: bonding: up/down delay w/ slave link flapping
https://git.kernel.org/netdev/net-next/c/d43eff0b85ae
- [net-next,v2,2/2] bonding: fix link recovery in mode 2 when updelay is nonzero
https://git.kernel.org/netdev/net-next/c/f8a65ab2f3ff
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:[~2022-11-24 4:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 20:25 [PATCH net-next v2 0/2] bonding: fix bond recovery in mode 2 Jonathan Toppins
2022-11-22 20:25 ` [PATCH net-next v2 1/2] selftests: bonding: up/down delay w/ slave link flapping Jonathan Toppins
2022-11-22 21:24 ` [PATCH net-next v2 2/2] bonding: fix link recovery in mode 2 when updelay is nonzero Jonathan Toppins
2022-11-23 6:25 ` Jay Vosburgh
2022-11-24 4: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=166926361627.22792.14683635371904949142.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=j.vosburgh@gmail.com \
--cc=jtoppins@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).