From: patchwork-bot+netdevbpf@kernel.org
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
UNGLinuxDriver@microchip.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net] net: lan966x: Fix assignment of the MAC address
Date: Tue, 17 May 2022 08:20:12 +0000 [thread overview]
Message-ID: <165277561220.28744.11715921270225705422.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220513180030.3076793-1-horatiu.vultur@microchip.com>
Hello:
This patch was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 13 May 2022 20:00:30 +0200 you wrote:
> The following two scenarios were failing for lan966x.
> 1. If the port had the address X and then trying to assign the same
> address, then the HW was just removing this address because first it
> tries to learn new address and then delete the old one. As they are
> the same the HW remove it.
> 2. If the port eth0 was assigned the same address as one of the other
> ports eth1 then when assigning back the address to eth0 then the HW
> was deleting the address of eth1.
>
> [...]
Here is the summary with links:
- [net] net: lan966x: Fix assignment of the MAC address
https://git.kernel.org/netdev/net/c/af8ca6eaa9b2
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-05-17 8:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 18:00 [PATCH net] net: lan966x: Fix assignment of the MAC address Horatiu Vultur
2022-05-17 8: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=165277561220.28744.11715921270225705422.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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