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,
linux-kselftest@vger.kernel.org, qren@redhat.com
Subject: Re: [PATCHv2 net 1/2] bonding: set random address only when slaves already exist
Date: Tue, 16 Sep 2025 01:00:09 +0000 [thread overview]
Message-ID: <175798440950.551080.8670014333406837115.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250910024336.400253-1-liuhangbin@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 10 Sep 2025 02:43:34 +0000 you wrote:
> After commit 5c3bf6cba791 ("bonding: assign random address if device
> address is same as bond"), bonding will erroneously randomize the MAC
> address of the first interface added to the bond if fail_over_mac =
> follow.
>
> Correct this by additionally testing for the bond being empty before
> randomizing the MAC.
>
> [...]
Here is the summary with links:
- [PATCHv2,net,1/2] bonding: set random address only when slaves already exist
https://git.kernel.org/netdev/net/c/35ae4e86292e
- [PATCHv2,net,2/2] selftests: bonding: add fail_over_mac testing
https://git.kernel.org/netdev/net/c/71379e1c95af
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:[~2025-09-16 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 2:43 [PATCHv2 net 1/2] bonding: set random address only when slaves already exist Hangbin Liu
2025-09-10 2:43 ` [PATCHv2 net 2/2] selftests: bonding: add fail_over_mac testing Hangbin Liu
2025-09-16 1:00 ` 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=175798440950.551080.8670014333406837115.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qren@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox