From: patchwork-bot+netdevbpf@kernel.org
To: Bhargava Chenna Marreddy <bhargava.marreddy@broadcom.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
michael.chan@broadcom.com, pavan.chebbi@broadcom.com,
vsrama-krishna.nemani@broadcom.com, vikas.gupta@broadcom.com
Subject: Re: [PATCH net-next v5 0/5] bnge: Make NQ0 persistent across open/close
Date: Sat, 21 Nov 2026 22:50:07 +0000 [thread overview]
Message-ID: <179530140703.1198296.17185704761543686840.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261117061641.122942-1-bhargava.marreddy@broadcom.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 17 Nov 2026 06:16:36 +0000 you wrote:
> Hi,
>
> This series ensures the bnge driver's Notification Queue 0 (NQ0) remains
> persistent across interface close/open cycles rather than being destroyed
> and recreated on each cycle.
>
> Currently, NQ0 exists only between ndo_open() and ndo_stop(), so firmware
> async events (e.g., link changes) and HWRM completions are not received
> while the interface is down.
>
> [...]
Here is the summary with links:
- [net-next,v5,1/5] bnge: factor out per-NQ alloc/free helpers
https://git.kernel.org/netdev/net-next/c/fd60aec4b427
- [net-next,v5,2/5] bnge: add bnge_err()/bnge_warn()/bnge_dbg() logging helpers
https://git.kernel.org/netdev/net-next/c/47a515a29e69
- [net-next,v5,3/5] bnge: add bnge_for_each_open_nq() iterator
https://git.kernel.org/netdev/net-next/c/e648e5ea36d4
- [net-next,v5,4/5] bnge: make irq_tbl layout depend on BNGE_FIRST_OPEN_NQ
https://git.kernel.org/netdev/net-next/c/15120271cc51
- [net-next,v5,5/5] bnge: create NQ0 during probe and keep it active across open/close
https://git.kernel.org/netdev/net-next/c/bcd72b750864
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-21 22:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 6:16 Bhargava Marreddy
2026-11-17 6:16 ` [PATCH net-next v5 1/5] bnge: factor out per-NQ alloc/free helpers Bhargava Marreddy
2026-11-17 6:16 ` [PATCH net-next v5 2/5] bnge: add bnge_err()/bnge_warn()/bnge_dbg() logging helpers Bhargava Marreddy
2026-11-17 6:16 ` [PATCH net-next v5 3/5] bnge: add bnge_for_each_open_nq() iterator Bhargava Marreddy
2026-11-20 11:18 ` Bhargava Chenna Marreddy
2026-11-17 6:16 ` [PATCH net-next v5 4/5] bnge: make irq_tbl layout depend on BNGE_FIRST_OPEN_NQ Bhargava Marreddy
2026-11-17 6:16 ` [PATCH net-next v5 5/5] bnge: create NQ0 during probe and keep it active across open/close Bhargava Marreddy
2026-11-21 22:50 ` 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=179530140703.1198296.17185704761543686840.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bhargava.marreddy@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=vikas.gupta@broadcom.com \
--cc=vsrama-krishna.nemani@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 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®