From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Marek_Beh=C3=BAn_=3Ckabel=40kernel=2Eorg=3E?=@ci.codeaurora.org
Cc: netdev@vger.kernel.org, andrew@lunn.ch, f.fainelli@gmail.com,
olteanv@gmail.com
Subject: Re: [PATCH net-next v3 0/2] Fix changing DSA conduit
Date: Mon, 10 Jun 2024 12:50:31 +0000 [thread overview]
Message-ID: <171802383188.19319.13366661293581709528.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240605133329.6304-1-kabel@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Wed, 5 Jun 2024 15:33:27 +0200 you wrote:
> This series fixes an issue in the DSA code related to host interface UC
> address installed into port FDB and port conduit address database when
> live-changing port conduit.
>
> The first patch refactores/deduplicates the installation/uninstallation
> of the interface's MAC address and the second patch fixes the issue.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] net: dsa: deduplicate code adding / deleting the port address to fdb
https://git.kernel.org/netdev/net-next/c/77f7541248fc
- [net-next,v3,2/2] net: dsa: update the unicast MAC address when changing conduit
https://git.kernel.org/netdev/net-next/c/eef8e906aea2
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:[~2024-06-10 12:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 13:33 [PATCH net-next v3 0/2] Fix changing DSA conduit Marek Behún
2024-06-05 13:33 ` [PATCH net-next v3 1/2] net: dsa: deduplicate code adding / deleting the port address to fdb Marek Behún
2024-06-05 14:15 ` Vladimir Oltean
2024-06-05 13:33 ` [PATCH net-next v3 2/2] net: dsa: update the unicast MAC address when changing conduit Marek Behún
2024-06-10 12:50 ` 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=171802383188.19319.13366661293581709528.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Marek_Beh=C3=BAn_=3Ckabel=40kernel=2Eorg=3E?=@ci.codeaurora.org \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.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 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.