From: patchwork-bot+netdevbpf@kernel.org
To: ALOK TIWARI <alok.a.tiwari@oracle.com>
Cc: sbhatta@marvell.com, hkelam@marvell.com, gakula@marvell.com,
lcherian@marvell.com, sgoutham@marvell.com,
andrew+netdev@lunn.ch, kuba@kernel.org, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, netdev@vger.kernel.org,
alok.a.tiwarilinux@gmail.com
Subject: Re: [PATCH 1/2] octeontx2-af: devlink: fix NIX RAS reporter recovery condition
Date: Thu, 12 Mar 2026 03:50:09 +0000 [thread overview]
Message-ID: <177328740955.3930157.15850300877882489500.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260310184824.1183651-1-alok.a.tiwari@oracle.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 10 Mar 2026 11:48:16 -0700 you wrote:
> The NIX RAS health reporter recovery routine checks nix_af_rvu_int to
> decide whether to re-enable NIX_AF_RAS interrupts. This is the RVU
> interrupt status field and is unrelated to RAS events, so the recovery
> flow may incorrectly skip re-enabling NIX_AF_RAS interrupts.
>
> Check nix_af_rvu_ras instead before writing NIX_AF_RAS_ENA_W1S.
>
> [...]
Here is the summary with links:
- [1/2] octeontx2-af: devlink: fix NIX RAS reporter recovery condition
https://git.kernel.org/netdev/net/c/dc26ca99b835
- [2/2] octeontx2-af: devlink: fix NIX RAS reporter to use RAS interrupt status
https://git.kernel.org/netdev/net/c/87f7dff3ec75
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-03-12 3:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 18:48 [PATCH 1/2] octeontx2-af: devlink: fix NIX RAS reporter recovery condition Alok Tiwari
2026-03-10 18:48 ` [PATCH 2/2] octeontx2-af: devlink: fix NIX RAS reporter to use RAS interrupt status Alok Tiwari
2026-03-12 3: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=177328740955.3930157.15850300877882489500.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=hkelam@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox