All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
	dw@davidwei.uk, jdamato@fastly.com, asml.silence@gmail.com,
	io-uring@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] selftests: drv-net: iou-zcrx: improve stability and make the large chunk test work
Date: Tue, 03 Mar 2026 04:47:04 +0000	[thread overview]
Message-ID: <177251322454.625663.6934806010207310713.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260227171305.2848240-1-kuba@kernel.org>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri, 27 Feb 2026 09:13:02 -0800 you wrote:
> The iou-zcrx test hasn't been passing in NIPA, I assumed it's because
> we're missing iouring changes, but it's still failing after the merge
> window. Turns out there was a bug in the implementation which was fixed
> separately via the iouring tree. With that out of the way the tests
> are passing but flaky. Patch 1 deals with the flakiness.
> 
> While looking at this I also noticed that the large chunk test isn't
> running at all. So fix and enable it (patches 2 and 3).
> 
> [...]

Here is the summary with links:
  - [net-next,1/3] selftests: drv-net: iou-zcrx: wait for memory provider cleanup
    https://git.kernel.org/netdev/net-next/c/27c4ab943882
  - [net-next,2/3] selftests: drv-net: iou-zcrx: rework large chunks test to use common setup
    https://git.kernel.org/netdev/net-next/c/67792dde27a6
  - [net-next,3/3] selftests: drv-net: iou-zcrx: allocate hugepages for large chunks test
    https://git.kernel.org/netdev/net-next/c/c7b228418e8b

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  4:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27 17:13 [PATCH net-next 0/3] selftests: drv-net: iou-zcrx: improve stability and make the large chunk test work Jakub Kicinski
2026-02-27 17:13 ` [PATCH net-next 1/3] selftests: drv-net: iou-zcrx: wait for memory provider cleanup Jakub Kicinski
2026-03-02 15:32   ` Dragos Tatulea
2026-03-02 15:49   ` David Wei
2026-03-03  0:46     ` Jakub Kicinski
2026-03-03  1:39       ` David Wei
2026-02-27 17:13 ` [PATCH net-next 2/3] selftests: drv-net: iou-zcrx: rework large chunks test to use common setup Jakub Kicinski
2026-03-02 15:54   ` David Wei
2026-03-03  0:48     ` Jakub Kicinski
2026-03-03  1:44       ` David Wei
2026-02-27 17:13 ` [PATCH net-next 3/3] selftests: drv-net: iou-zcrx: allocate hugepages for large chunks test Jakub Kicinski
2026-03-02 15:16   ` Dragos Tatulea
2026-03-03  2:22     ` Jakub Kicinski
2026-03-03  8:41       ` Dragos Tatulea
2026-03-03  4:47 ` 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=177251322454.625663.6934806010207310713.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=asml.silence@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dw@davidwei.uk \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=io-uring@vger.kernel.org \
    --cc=jdamato@fastly.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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.