From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw141117 [PATCH v2 8/8] net/mlx5: add async flow operation validation
Date: Wed, 12 Jun 2024 18:26:57 +0200 (CEST) [thread overview]
Message-ID: <20240612162657.22B91124124@dpdk.org> (raw)
In-Reply-To: <20240612162426.978117-9-dsosnowski@nvidia.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/141117
_coding style OK_
next prev parent reply other threads:[~2024-06-12 16:26 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240612162426.978117-9-dsosnowski@nvidia.com>
2024-06-12 16:00 ` |SUCCESS| pw141110-141117 " qemudev
2024-06-12 16:05 ` qemudev
2024-06-12 16:26 ` checkpatch [this message]
2024-06-13 2:00 ` |WARNING| pw141110-141117 [PATCH] [v2,8/8] net/mlx5: add async flow dpdklab
2024-06-13 2:12 ` dpdklab
2024-06-13 2:41 ` dpdklab
2024-06-13 2:42 ` dpdklab
2024-06-13 3:26 ` dpdklab
2024-06-13 3:32 ` dpdklab
2024-06-13 3:38 ` dpdklab
2024-06-13 3:43 ` dpdklab
2024-06-13 3:56 ` dpdklab
2024-06-13 4:17 ` dpdklab
2024-06-13 4:18 ` dpdklab
2024-06-13 4:50 ` |FAILURE| " dpdklab
2024-06-13 4:50 ` dpdklab
2024-06-13 4:51 ` dpdklab
2024-06-13 4:51 ` dpdklab
2024-06-13 4:51 ` dpdklab
2024-06-13 4:51 ` dpdklab
2024-06-13 4:51 ` dpdklab
2024-06-13 4:51 ` dpdklab
2024-06-13 4:51 ` dpdklab
2024-06-13 4:51 ` dpdklab
2024-06-13 4:51 ` dpdklab
2024-06-13 4:51 ` dpdklab
2024-06-13 4:52 ` dpdklab
2024-06-13 4:52 ` dpdklab
2024-06-13 4:52 ` dpdklab
2024-06-13 4:52 ` dpdklab
2024-06-13 4:52 ` dpdklab
2024-06-13 4:52 ` dpdklab
2024-06-13 4:52 ` dpdklab
2024-06-13 4:52 ` dpdklab
2024-06-13 4:53 ` dpdklab
2024-06-13 4:53 ` dpdklab
2024-06-13 4:53 ` dpdklab
2024-06-13 4:53 ` dpdklab
2024-06-13 4:53 ` dpdklab
2024-06-13 4:54 ` dpdklab
2024-06-13 4:54 ` dpdklab
2024-06-13 4:54 ` dpdklab
2024-06-13 4:54 ` dpdklab
2024-06-13 4:55 ` |WARNING| " dpdklab
2024-06-13 4:55 ` |FAILURE| " dpdklab
2024-06-13 4:55 ` dpdklab
2024-06-13 4:56 ` dpdklab
2024-06-13 4:56 ` dpdklab
2024-06-13 4:56 ` dpdklab
2024-06-13 4:57 ` dpdklab
2024-06-13 4:57 ` dpdklab
2024-06-13 4:57 ` |WARNING| " dpdklab
2024-06-13 4:58 ` |FAILURE| " dpdklab
2024-06-13 4:58 ` dpdklab
2024-06-13 4:58 ` dpdklab
2024-06-13 4:59 ` dpdklab
2024-06-13 4:59 ` dpdklab
2024-06-13 5:00 ` dpdklab
2024-06-13 5:00 ` dpdklab
2024-06-13 5:00 ` dpdklab
2024-06-13 5:01 ` dpdklab
2024-06-13 5:01 ` dpdklab
2024-06-13 5:02 ` dpdklab
2024-06-13 5:02 ` dpdklab
2024-06-13 5:02 ` dpdklab
2024-06-13 5:02 ` dpdklab
2024-06-13 5:03 ` dpdklab
2024-06-13 5:03 ` dpdklab
2024-06-13 5:04 ` dpdklab
2024-06-13 5:04 ` dpdklab
2024-06-13 5:04 ` dpdklab
2024-06-13 5:05 ` dpdklab
2024-06-13 5:06 ` dpdklab
2024-06-13 5:07 ` dpdklab
2024-06-13 5:07 ` dpdklab
2024-06-13 5:10 ` dpdklab
2024-06-13 5:10 ` |WARNING| " dpdklab
2024-06-13 5:10 ` |FAILURE| " dpdklab
2024-06-13 5:22 ` dpdklab
2024-06-13 5:22 ` dpdklab
2024-06-13 5:23 ` dpdklab
2024-06-13 5:23 ` dpdklab
2024-06-13 5:24 ` dpdklab
2024-06-13 5:25 ` dpdklab
2024-06-13 5:31 ` 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=20240612162657.22B91124124@dpdk.org \
--to=checkpatch@dpdk.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).