mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: <Tristram.Ha@microchip.com>
Cc: woojung.huh@microchip.com, arun.ramadoss@microchip.com,
	andrew@lunn.ch, olteanv@gmail.com, linux@rempel-privat.de,
	lukma@nabladev.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, UNGLinuxDriver@microchip.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	tristram.ha@microchip.com
Subject: Re: [PATCH net v2] net: dsa: microchip: Fix reserved multicast address table programming
Date: Thu, 06 Nov 2025 15:20:05 +0000	[thread overview]
Message-ID: <176244240551.248343.15383684088656662475.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251105033741.6455-1-Tristram.Ha@microchip.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 4 Nov 2025 19:37:41 -0800 you wrote:
> From: Tristram Ha <tristram.ha@microchip.com>
> 
> KSZ9477/KSZ9897 and LAN937X families of switches use a reserved multicast
> address table for some specific forwarding with some multicast addresses,
> like the one used in STP.  The hardware assumes the host port is the last
> port in KSZ9897 family and port 5 in LAN937X family.  Most of the time
> this assumption is correct but not in other cases like KSZ9477.
> Originally the function just setups the first entry, but the others still
> need update, especially for one common multicast address that is used by
> PTP operation.
> 
> [...]

Here is the summary with links:
  - [net,v2] net: dsa: microchip: Fix reserved multicast address table programming
    https://git.kernel.org/netdev/net/c/96baf482ca1f

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2025-11-06 15:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05  3:37 Tristram.Ha
2025-11-06 15: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=176244240551.248343.15383684088656662475.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=Tristram.Ha@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=arun.ramadoss@microchip.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rempel-privat.de \
    --cc=lukma@nabladev.com \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=woojung.huh@microchip.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
all inboxes | Powered by JetHome®