From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw140920 [PATCH v3 3/3] compress/uadk: support burst enqueue/dequeue
Date: Tue, 11 Jun 2024 09:10:44 +0200 (CEST) [thread overview]
Message-ID: <20240611071044.4B842124124@dpdk.org> (raw)
In-Reply-To: <20240611070726.468-4-zhangfei.gao@linaro.org>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/140920
_coding style OK_
next prev parent reply other threads:[~2024-06-11 7:10 UTC|newest]
Thread overview: 113+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240611070726.468-4-zhangfei.gao@linaro.org>
2024-06-11 6:53 ` |SUCCESS| pw140918-140920 " qemudev
2024-06-11 6:58 ` qemudev
2024-06-11 7:10 ` checkpatch [this message]
2024-06-11 8:04 ` |SUCCESS| pw140920 " 0-day Robot
2024-06-11 14:20 ` |SUCCESS| pw140918-140920 [PATCH] [v3,3/3] compress/uadk: support bu dpdklab
2024-06-11 14:21 ` dpdklab
2024-06-11 14:32 ` dpdklab
2024-06-11 14:58 ` dpdklab
2024-06-11 15:01 ` dpdklab
2024-06-11 15:08 ` dpdklab
2024-06-13 0:40 ` dpdklab
2024-06-13 0:40 ` dpdklab
2024-06-13 0:40 ` dpdklab
2024-06-13 0:41 ` dpdklab
2024-06-13 0:41 ` dpdklab
2024-06-13 0:41 ` dpdklab
2024-06-13 0:42 ` dpdklab
2024-06-13 0:42 ` dpdklab
2024-06-13 0:42 ` dpdklab
2024-06-13 0:42 ` dpdklab
2024-06-13 0:42 ` dpdklab
2024-06-13 0:42 ` dpdklab
2024-06-13 0:43 ` dpdklab
2024-06-13 0:43 ` dpdklab
2024-06-13 0:43 ` dpdklab
2024-06-13 0:43 ` dpdklab
2024-06-13 0:44 ` dpdklab
2024-06-13 0:44 ` dpdklab
2024-06-13 0:45 ` dpdklab
2024-06-13 0:45 ` dpdklab
2024-06-13 0:45 ` dpdklab
2024-06-13 0:45 ` dpdklab
2024-06-13 0:45 ` dpdklab
2024-06-13 0:45 ` dpdklab
2024-06-13 0:46 ` dpdklab
2024-06-13 0:46 ` |FAILURE| " dpdklab
2024-06-13 0:46 ` |SUCCESS| " dpdklab
2024-06-13 0:46 ` dpdklab
2024-06-13 0:46 ` dpdklab
2024-06-13 0:47 ` dpdklab
2024-06-13 0:47 ` dpdklab
2024-06-13 0:47 ` dpdklab
2024-06-13 0:47 ` |FAILURE| " dpdklab
2024-06-13 0:48 ` dpdklab
2024-06-13 0:48 ` dpdklab
2024-06-13 0:48 ` |SUCCESS| " dpdklab
2024-06-13 0:48 ` dpdklab
2024-06-13 0:49 ` |FAILURE| " dpdklab
2024-06-13 0:49 ` dpdklab
2024-06-13 0:49 ` dpdklab
2024-06-13 0:49 ` dpdklab
2024-06-13 0:49 ` |SUCCESS| " dpdklab
2024-06-13 0:49 ` dpdklab
2024-06-13 0:49 ` dpdklab
2024-06-13 0:49 ` dpdklab
2024-06-13 0:49 ` dpdklab
2024-06-13 0:50 ` dpdklab
2024-06-13 0:50 ` dpdklab
2024-06-13 0:50 ` dpdklab
2024-06-13 0:51 ` dpdklab
2024-06-13 0:51 ` |FAILURE| " dpdklab
2024-06-13 0:53 ` |SUCCESS| " dpdklab
2024-06-13 0:53 ` dpdklab
2024-06-13 0:54 ` dpdklab
2024-06-13 0:54 ` |FAILURE| " dpdklab
2024-06-13 0:54 ` |SUCCESS| " dpdklab
2024-06-13 0:54 ` |FAILURE| " dpdklab
2024-06-13 0:54 ` |SUCCESS| " dpdklab
2024-06-13 0:55 ` |FAILURE| " dpdklab
2024-06-13 0:55 ` dpdklab
2024-06-13 0:56 ` dpdklab
2024-06-13 0:57 ` dpdklab
2024-06-13 0:57 ` dpdklab
2024-06-13 0:57 ` |SUCCESS| " dpdklab
2024-06-13 0:58 ` |FAILURE| " dpdklab
2024-06-13 0:58 ` dpdklab
2024-06-13 0:58 ` |SUCCESS| " dpdklab
2024-06-13 1:00 ` dpdklab
2024-06-13 1:00 ` dpdklab
2024-06-13 1:00 ` dpdklab
2024-06-13 1:00 ` dpdklab
2024-06-13 1:00 ` dpdklab
2024-06-13 1:01 ` dpdklab
2024-06-13 1:01 ` dpdklab
2024-06-13 1:01 ` dpdklab
2024-06-13 1:02 ` dpdklab
2024-06-13 1:02 ` dpdklab
2024-06-13 1:02 ` dpdklab
2024-06-13 1:02 ` dpdklab
2024-06-13 1:02 ` dpdklab
2024-06-13 1:02 ` dpdklab
2024-06-13 1:02 ` dpdklab
2024-06-13 1:02 ` dpdklab
2024-06-13 1:03 ` dpdklab
2024-06-13 1:03 ` dpdklab
2024-06-13 1:03 ` dpdklab
2024-06-13 1:03 ` dpdklab
2024-06-13 1:03 ` dpdklab
2024-06-13 1:03 ` dpdklab
2024-06-13 1:04 ` dpdklab
2024-06-13 1:05 ` dpdklab
2024-06-13 1:05 ` dpdklab
2024-06-13 1:05 ` dpdklab
2024-06-13 1:05 ` dpdklab
2024-06-13 1:05 ` dpdklab
2024-06-13 1:06 ` dpdklab
2024-06-13 1:06 ` dpdklab
2024-06-13 1:06 ` dpdklab
2024-06-13 1:06 ` dpdklab
2024-06-13 1:06 ` dpdklab
2024-06-13 1:08 ` dpdklab
2024-06-13 1:09 ` dpdklab
2024-06-13 1:15 ` 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=20240611071044.4B842124124@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).