All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Rosen Penev <rosenp@gmail.com>
Cc: netdev@vger.kernel.org, rafal@milecki.pl,
	bcm-kernel-feedback-list@broadcom.com, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
	pabeni@redhat.com, jon.mason@broadcom.com, f.fainelli@gmail.com,
	zhongx@broadcom.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: bgmac: enable interrupts only after NAPI is ready
Date: Fri, 16 Oct 2026 02:20:06 +0000	[thread overview]
Message-ID: <179211720602.18595.409341972831796996.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261010070011.60403-1-rosenp@gmail.com>

Hello:

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

On Sat, 10 Oct 2026 00:00:11 -0700 you wrote:
> bgmac_open() calls bgmac_chip_init(), which unmasks the interrupts and
> enables the MAC receiver, before request_irq() and napi_enable().
> bgmac_enet_resume() also enables NAPI only after bgmac_chip_init().
> 
> When frames arrive in that window, the first RX interrupt masks all
> interrupts in bgmac_interrupt() and calls napi_schedule() on a NAPI
> instance that is still disabled, so nothing is scheduled. Nothing
> unmasks the interrupts again, the RX ring fills up and the interface
> stays deaf until it is brought down and up without traffic.
> 
> [...]

Here is the summary with links:
  - [net] net: bgmac: enable interrupts only after NAPI is ready
    https://git.kernel.org/netdev/net-next/c/ac1f6e58cb77

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-10-16  2:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-10  7:00 [PATCH net] net: bgmac: enable interrupts only after NAPI is ready Rosen Penev
2026-10-12  6:43 ` Daniel Machon
2026-10-16  2: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=179211720602.18595.409341972831796996.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=jon.mason@broadcom.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rafal@milecki.pl \
    --cc=rosenp@gmail.com \
    --cc=zhongx@broadcom.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.