From: patchwork-bot+netdevbpf@kernel.org
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org, j.vosburgh@gmail.com,
davem@davemloft.net, kuba@kernel.org, jtoppins@redhat.com,
pabeni@redhat.com, edumazet@google.com, liali@redhat.com,
saeed@kernel.org
Subject: Re: [PATCH net 0/3] Bonding: fix high prio not effect issue
Date: Wed, 14 Dec 2022 03:30:17 +0000 [thread overview]
Message-ID: <167098861748.20181.2346186639120427683.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221212035647.1053865-1-liuhangbin@gmail.com>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 12 Dec 2022 11:56:44 +0800 you wrote:
> When a high prio link up, if there has current link, it will not do
> failover as we missed the check in link up event. Fix it in this patchset
> and add a prio option test case.
>
> v2:
> 1. use rcu_access_pointer() instead of rtnl_dereference().
> 2: make do_failover after looping all slaves
>
> [...]
Here is the summary with links:
- [PATCHv2,net,1/3] bonding: add missed __rcu annotation for curr_active_slave
https://git.kernel.org/netdev/net/c/3d0b738fc5ad
- [PATCHv2,net,2/3] bonding: do failover when high prio link up
https://git.kernel.org/netdev/net/c/e95cc44763a4
- [PATCHv2,net,3/3] selftests: bonding: add bonding prio option test
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-12-14 3:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 3:56 [PATCH net 0/3] Bonding: fix high prio not effect issue Hangbin Liu
2022-12-12 3:56 ` [PATCHv2 net 1/3] bonding: add missed __rcu annotation for curr_active_slave Hangbin Liu
2022-12-12 3:56 ` [PATCHv2 net 2/3] bonding: do failover when high prio link up Hangbin Liu
2022-12-12 3:56 ` [PATCHv2 net 3/3] selftests: bonding: add bonding prio option test Hangbin Liu
2022-12-14 3:30 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-09 10:13 [PATCH net 0/3] Bonding: fix high prio not effect issue Hangbin Liu
2022-12-10 0:01 ` Jay Vosburgh
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=167098861748.20181.2346186639120427683.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=j.vosburgh@gmail.com \
--cc=jtoppins@redhat.com \
--cc=kuba@kernel.org \
--cc=liali@redhat.com \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeed@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.