Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH net-next] net: lan966x: Add spinlock for frame transmission
 from CPU.
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <164683801456.7970.18419622051031308474.git-patchwork-notify@kernel.org>
Date:   Wed, 09 Mar 2022 15:00:14 +0000
References: <20220308102904.3978779-1-horatiu.vultur@microchip.com>
In-Reply-To: <20220308102904.3978779-1-horatiu.vultur@microchip.com>
To:     Horatiu Vultur <horatiu.vultur@microchip.com>
Cc:     netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
        UNGLinuxDriver@microchip.com, davem@davemloft.net, kuba@kernel.org
Precedence: bulk

Hello:

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

On Tue, 8 Mar 2022 11:29:04 +0100 you wrote:
> The registers used to inject a frame to one of the ports is shared
> between all the net devices. Therefore, there can be race conditions for
> accessing the registers when two processes send frames at the same time
> on different ports.
> 
> To fix this, add a spinlock around the function
> 'lan966x_port_ifh_xmit()'.
> 
> [...]

Here is the summary with links:
  - [net-next] net: lan966x: Add spinlock for frame transmission from CPU.
    https://git.kernel.org/netdev/net-next/c/0dbdf819f4c1

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