mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Machon <daniel.machon@microchip.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
	kuba@kernel.org, pabeni@redhat.com, Steen.Hegelund@microchip.com,
	UNGLinuxDriver@microchip.com, memoriaru@foxmail.com,
	netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/2] net: sparx5/lan969x: fix RX ring stall on frames from inactive ports
Date: Wed, 18 Nov 2026 03:00:05 +0000	[thread overview]
Message-ID: <179497080553.1433107.371747421258981777.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261116-sparx5-rx-inactive-port-v1-0-343d8bab58bb@microchip.com>

Hello:

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

On Mon, 16 Nov 2026 10:56:03 +0100 you wrote:
> On Sparx5 and lan969x, a received frame whose source port does not map
> to an active port is never consumed from the FDMA RX ring: the NAPI poll
> stops on it, and finds the same DB again on every following poll.
> 
> Patch 1 fixes Sparx5, where the same skb grows on every poll until
> skb_over_panic().
> 
> [...]

Here is the summary with links:
  - [net,1/2] net: sparx5: fix RX ring stall on frames from inactive ports
    https://git.kernel.org/netdev/net/c/81d2cf1c6d56
  - [net,2/2] net: lan969x: fix RX ring stall on frames from inactive ports
    https://git.kernel.org/netdev/net/c/1a47bc214d00

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



      parent reply	other threads:[~2026-11-18  3:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16  9:56 Daniel Machon
2026-11-16  9:56 ` [PATCH net 1/2] net: sparx5: " Daniel Machon
2026-11-16  9:56 ` [PATCH net 2/2] net: lan969x: " Daniel Machon
2026-11-18  3:00 ` 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=179497080553.1433107.371747421258981777.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=Steen.Hegelund@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=daniel.machon@microchip.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=memoriaru@foxmail.com \
    --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

all inboxes | Powered by JetHome®