public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Vimlesh Kumar <vimleshk@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	sedara@marvell.com, srasheed@marvell.com, hgani@marvell.com
Subject: Re: [PATCH net v2 0/4] avoid compiler and IQ/OQ reordering
Date: Tue, 03 Mar 2026 10:40:12 +0000	[thread overview]
Message-ID: <177253441229.791831.6108494712543738989.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260227091402.1773833-1-vimleshk@marvell.com>

Hello:

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

On Fri, 27 Feb 2026 09:13:56 +0000 you wrote:
> Utilize READ_ONCE and WRITE_ONCE APIs to prevent compiler
> optimization and reordering. Ensure IO queue OUT/IN_CNT
> registers are flushed. Relocate IQ/OQ IN/OUT_CNTS updates
> to occur before NAPI completion, and replace napi_complete
> with napi_complete_done.
> 
> Vimlesh Kumar (4):
>   octeon_ep: Relocate counter updates before NAPI
>   octeon_ep: avoid compiler and IQ/OQ reordering
>   octeon_ep_vf: Relocate counter updates before NAPI
>   octeon_ep_vf: avoid compiler and IQ/OQ reordering
> 
> [...]

Here is the summary with links:
  - [net,v2,1/4] octeon_ep: Relocate counter updates before NAPI
    https://git.kernel.org/netdev/net/c/18c04a808c43
  - [net,v2,2/4] octeon_ep: avoid compiler and IQ/OQ reordering
    https://git.kernel.org/netdev/net/c/43b3160cb639
  - [net,v2,3/4] octeon_ep_vf: Relocate counter updates before NAPI
    https://git.kernel.org/netdev/net/c/2ae7d20fb24f
  - [net,v2,4/4] octeon_ep_vf: avoid compiler and IQ/OQ reordering
    https://git.kernel.org/netdev/net/c/6c73126ecd10

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-03-03 10:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27  9:13 [PATCH net v2 0/4] avoid compiler and IQ/OQ reordering Vimlesh Kumar
2026-02-27  9:13 ` [PATCH net v2 1/4] octeon_ep: Relocate counter updates before NAPI Vimlesh Kumar
2026-02-27  9:13 ` [PATCH net v2 2/4] octeon_ep: avoid compiler and IQ/OQ reordering Vimlesh Kumar
2026-02-27  9:13 ` [PATCH net v2 3/4] octeon_ep_vf: Relocate counter updates before NAPI Vimlesh Kumar
2026-02-27  9:14 ` [PATCH net v2 4/4] octeon_ep_vf: avoid compiler and IQ/OQ reordering Vimlesh Kumar
2026-03-03 10:40 ` 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=177253441229.791831.6108494712543738989.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=hgani@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sedara@marvell.com \
    --cc=srasheed@marvell.com \
    --cc=vimleshk@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