From: patchwork-bot+netdevbpf@kernel.org
To: Alok Tiwari <alok.a.tiwari@oracle.com>
Cc: sbhatta@marvell.com, hkelam@marvell.com, jerinj@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 net-next] octeontx2-af: make PF_FUNC comparison consistent in NIX XOFF handling
Date: Fri, 06 Mar 2026 03:33:03 +0000 [thread overview]
Message-ID: <177276798304.3348267.12480565302628692815.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260304193950.2467391-1-alok.a.tiwari@oracle.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 4 Mar 2026 11:39:48 -0800 you wrote:
> nix_smq_flush_enadis_xoff() compares PF_FUNC values with the FUNC bits
> masked off, but one operand applied the mask before extracting PF_FUNC
> via TXSCH_MAP_FUNC().
>
> Apply RVU_PFVF_FUNC_MASK after TXSCH_MAP_FUNC() for the TL2 scheduler
> queue operand, matching the existing handling of the other operand and
> making the comparison consistent and clearer.
>
> [...]
Here is the summary with links:
- [net-next] octeontx2-af: make PF_FUNC comparison consistent in NIX XOFF handling
https://git.kernel.org/netdev/net-next/c/58a4c3e80065
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-06 3:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 19:39 [PATCH net-next] octeontx2-af: make PF_FUNC comparison consistent in NIX XOFF handling Alok Tiwari
2026-03-05 6:28 ` Subbaraya Sundeep
2026-03-06 3:33 ` 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=177276798304.3348267.12480565302628692815.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=jerinj@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