From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw148389 [PATCH] net/mlx5: fix Rx queue ref count in flushing user flows
Date: Wed, 13 Nov 2024 03:25:35 -0500 [thread overview]
Message-ID: <20241113082535.2552434-1-robot@bytheb.org> (raw)
In-Reply-To: <20241113072244.7627-1-bingz@nvidia.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/148389/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/11812831164
next prev parent reply other threads:[~2024-11-13 8:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241113072244.7627-1-bingz@nvidia.com>
2024-11-13 6:54 ` qemudev
2024-11-13 6:59 ` qemudev
2024-11-13 7:23 ` checkpatch
2024-11-13 8:25 ` 0-day Robot [this message]
2024-11-13 14:25 ` |SUCCESS| pw148389 [PATCH] net/mlx5: fix Rx queue ref count in flush dpdklab
2024-11-13 14:48 ` dpdklab
2024-11-13 15:00 ` dpdklab
2024-11-13 16:30 ` dpdklab
2024-11-13 16:31 ` dpdklab
2024-11-13 16:52 ` dpdklab
2024-11-13 18:44 ` |PENDING| " dpdklab
2024-11-13 19:05 ` dpdklab
2024-11-13 19:08 ` |SUCCESS| " dpdklab
2024-11-13 19:52 ` dpdklab
2024-11-13 20:14 ` dpdklab
2024-11-13 20:18 ` dpdklab
2024-11-13 20:53 ` dpdklab
2024-11-13 20:57 ` dpdklab
2024-11-13 20:57 ` |PENDING| " dpdklab
2024-11-13 21:07 ` dpdklab
2024-11-13 21:08 ` |SUCCESS| " dpdklab
2024-11-13 21:44 ` |WARNING| " dpdklab
2024-11-13 23:12 ` dpdklab
2024-11-13 23:13 ` |SUCCESS| " dpdklab
2024-11-13 23:24 ` dpdklab
2024-11-14 16:56 ` |WARNING| " dpdklab
2024-11-14 20:08 ` |SUCCESS| " dpdklab
2024-11-14 20:47 ` dpdklab
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=20241113082535.2552434-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=test-report@dpdk.org \
/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;
as well as URLs for NNTP newsgroup(s).