From: patchwork-bot+netdevbpf@kernel.org
To: Feng zhou <zhoufeng.zf@bytedance.com>
Cc: axboe@kernel.dk, asml.silence@gmail.com, almasrymina@google.com,
kuba@kernel.org, edumazet@google.com, pabeni@redhat.com,
horms@kernel.org, saeedm@nvidia.com, tariqt@nvidia.co,
mbloch@nvidia.com, leon@kernel.org, andrew+netdev@lunn.ch,
dtatulea@nvidia.com, netdev@vger.kernel.org,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
yangzhenze@bytedance.com, wangdongdong.6@bytedance.com
Subject: Re: [PATCH net-next] io_uring/zcrx: fix ifq->if_rxq is -1, get dma_dev is NULL
Date: Tue, 16 Sep 2025 01:30:40 +0000 [thread overview]
Message-ID: <175798624024.559370.11569066407695924130.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250912140133.97741-1-zhoufeng.zf@bytedance.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 12 Sep 2025 22:01:33 +0800 you wrote:
> From: Feng Zhou <zhoufeng.zf@bytedance.com>
>
> ifq->if_rxq has not been assigned, is -1, the correct value is
> in reg.if_rxq.
>
> Fixes: 59b8b32ac8d469958936fcea781c7f58e3d64742 ("io_uring/zcrx: add support for custom DMA devices")
> Signed-off-by: Feng Zhou <zhoufeng.zf@bytedance.com>
>
> [...]
Here is the summary with links:
- [net-next] io_uring/zcrx: fix ifq->if_rxq is -1, get dma_dev is NULL
https://git.kernel.org/netdev/net-next/c/3a0ac202534b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-09-16 1:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 14:01 [PATCH net-next] io_uring/zcrx: fix ifq->if_rxq is -1, get dma_dev is NULL Feng zhou
2025-09-15 19:36 ` Jens Axboe
2025-09-16 1:30 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-12 8:39 Feng zhou
2025-09-12 12:40 ` Pavel Begunkov
2025-09-12 14:22 ` Jakub Kicinski
2025-09-12 18:30 ` Mina Almasry
2025-09-15 15:14 ` Pavel Begunkov
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=175798624024.559370.11569066407695924130.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=io-uring@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.co \
--cc=wangdongdong.6@bytedance.com \
--cc=yangzhenze@bytedance.com \
--cc=zhoufeng.zf@bytedance.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.