From: patchwork-bot+netdevbpf@kernel.org
To: Fernando Fernandez Mancera <ffmancera@riseup.net>
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
shannon.nelson@amd.com, horms@kernel.org, lukma@denx.de,
kuba@kernel.org
Subject: Re: [PATCH v3 net-next] net: hsr: sync hw addr of slave2 according to slave1 hw addr on PRP
Date: Mon, 14 Apr 2025 11:51:20 +0000 [thread overview]
Message-ID: <174463148062.1862892.15248243101265815428.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250409101911.3120-1-ffmancera@riseup.net>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Wed, 9 Apr 2025 12:19:11 +0200 you wrote:
> In order to work properly PRP requires slave1 and slave2 to share the
> same MAC address. To ease the configuration process on userspace tools,
> sync the slave2 MAC address with slave1. In addition, when deleting the
> port from the list, restore the original MAC address.
>
> Signed-off-by: Fernando Fernandez Mancera <ffmancera@riseup.net>
>
> [...]
Here is the summary with links:
- [v3,net-next] net: hsr: sync hw addr of slave2 according to slave1 hw addr on PRP
https://git.kernel.org/netdev/net-next/c/b65999e7238e
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:[~2025-04-14 11:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 10:19 [PATCH v3 net-next] net: hsr: sync hw addr of slave2 according to slave1 hw addr on PRP Fernando Fernandez Mancera
2025-04-14 11:51 ` patchwork-bot+netdevbpf [this message]
2026-03-29 15:07 ` Luka Gejak
2026-03-29 16:58 ` Fernando Fernandez Mancera
2026-03-29 17:19 ` Luka Gejak
2026-03-29 17:22 ` Fernando Fernandez Mancera
2026-03-29 17:32 ` Luka Gejak
2026-03-29 17:46 ` Fernando Fernandez Mancera
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=174463148062.1862892.15248243101265815428.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=edumazet@google.com \
--cc=ffmancera@riseup.net \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=lukma@denx.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shannon.nelson@amd.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