Received-SPF: pass (google.com: domain of linux-kernel+bounces-81294-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH net-next v3 1/1] net: dsa: microchip: Add support for bridge
 port isolation
From: patchwork-bot+netdevbpf@kernel.org
Message-Id: 
 <170894763206.4235.9816052153130545658.git-patchwork-notify@kernel.org>
Date: Mon, 26 Feb 2024 11:40:32 +0000
References: <20240222075113.2564540-1-o.rempel@pengutronix.de>
In-Reply-To: <20240222075113.2564540-1-o.rempel@pengutronix.de>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: davem@davemloft.net, andrew@lunn.ch, edumazet@google.com,
 f.fainelli@gmail.com, kuba@kernel.org, pabeni@redhat.com, olteanv@gmail.com,
 woojung.huh@microchip.com, arun.ramadoss@microchip.com,
 kernel@pengutronix.de, linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
 UNGLinuxDriver@microchip.com

Hello:

This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:

On Thu, 22 Feb 2024 08:51:13 +0100 you wrote:
> Implement bridge port isolation for KSZ switches. Enabling the isolation
> of switch ports from each other while maintaining connectivity with the
> CPU and other forwarding ports. For instance, to isolate swp1 and swp2
> from each other, use the following commands:
> - bridge link set dev swp1 isolated on
> - bridge link set dev swp2 isolated on
> 
> [...]

Here is the summary with links:
  - [net-next,v3,1/1] net: dsa: microchip: Add support for bridge port isolation
    https://git.kernel.org/netdev/net-next/c/a7f08029e2e8

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