From: patchwork-bot+netdevbpf@kernel.org
To: Eric Joyner <eric.joyner@amd.com>
Cc: netdev@vger.kernel.org, brett.creeley@amd.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, prabu.ponrajthayalan@amd.com,
nikhil.rao@amd.com
Subject: Re: [PATCH net 0/2] ionic: fix completion descriptor access
Date: Mon, 17 Aug 2026 20:00:14 +0000 [thread overview]
Message-ID: <178699681464.1714062.14061885744342067780.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260811195039.1315045-1-eric.joyner@amd.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 11 Aug 2026 12:50:37 -0700 you wrote:
> The first patch adds the missing dma_rmb() between the completion
> publish checks and the reads of the descriptor payloads, suggested by
> the Sashiko review from [1] for the second patch.
>
> The second locates the completion within its slot from cq->desc_size
> rather than a fixed stride, which is necessary when IONIC_Q_F_2X_CQ_DESC
> (double-sized completion descriptors) is used (e.g. for hardware
> timestamps).
>
> [...]
Here is the summary with links:
- [net,1/2] ionic: add missing dma_rmb() after the completion publish check
https://git.kernel.org/netdev/net/c/621f44af8c5b
- [net,2/2] ionic: fix completion descriptor access with 2x desc size
https://git.kernel.org/netdev/net/c/5da6ec6f06f2
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-08-17 20:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 19:50 [PATCH net 0/2] ionic: fix completion descriptor access Eric Joyner
2026-08-11 19:50 ` [PATCH net 1/2] ionic: add missing dma_rmb() after the completion publish check Eric Joyner
2026-08-11 19:50 ` [PATCH net 2/2] ionic: fix completion descriptor access with 2x desc size Eric Joyner
2026-08-13 13:53 ` [PATCH net 0/2] ionic: fix completion descriptor access Simon Horman
2026-08-17 20:00 ` 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=178699681464.1714062.14061885744342067780.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.joyner@amd.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikhil.rao@amd.com \
--cc=pabeni@redhat.com \
--cc=prabu.ponrajthayalan@amd.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.