All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Alok Tiwari <alok.a.tiwari@oracle.com>
Cc: sbhatta@marvell.com, gakula@marvell.com, sgoutham@marvell.com,
	rkannoth@marvell.com, skardach@marvell.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
	alok.a.tiwarilinux@gmail.com
Subject: Re: [PATCH net] octeontx2-af: Fix CQ enable state tracking after AQ writes
Date: Mon, 19 Oct 2026 09:30:05 +0000	[thread overview]
Message-ID: <179240220517.2517745.4701100148658848957.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261011125508.534618-1-alok.a.tiwari@oracle.com>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Sun, 11 Oct 2026 05:54:59 -0700 you wrote:
> Use the CQ context's ena field when updating the CQ enable bitmap.
> The current code reads rq.ena, which overlaps bit 0 of the CQ base address
> and can leave the bitmap out of sync with the hardware context. This can
> cause enabled CQs to be skipped during teardown.
> 
> Use sq.ena for the SQ bitmap update as well, so each queue type reads
> its own context.
> 
> [...]

Here is the summary with links:
  - [net] octeontx2-af: Fix CQ enable state tracking after AQ writes
    https://git.kernel.org/netdev/net/c/07bd391eb957

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-19  9:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-11 12:54 [PATCH net] octeontx2-af: Fix CQ enable state tracking after AQ writes Alok Tiwari
2026-10-11 12:59 ` netdev-bot+sinfo
2026-10-12  4:00 ` Ratheesh Kannoth
2026-10-12 11:44 ` [EXTERNAL] " Sunil Kovvuri Goutham
2026-10-19  9:30 ` 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=179240220517.2517745.4701100148658848957.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alok.a.tiwari@oracle.com \
    --cc=alok.a.tiwarilinux@gmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gakula@marvell.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rkannoth@marvell.com \
    --cc=sbhatta@marvell.com \
    --cc=sgoutham@marvell.com \
    --cc=skardach@marvell.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.