From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137690 [PATCH] examples/l3fwd: fix Rx over not ready port
Date: Sat, 2 Mar 2024 10:43:52 +0800 [thread overview]
Message-ID: <202403020243.4222hqBj3455894@localhost.localdomain> (raw)
In-Reply-To: <20240301163931.107036-1-konstantin.v.ananyev@yandex.ru>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/137690
_Compilation OK_
Submitter: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Date: Fri, 1 Mar 2024 16:39:31 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 5df34de5808a7b826b8bc035d6ee3161a12be364
137690 --> meson & ninja build successfully
Test environment and result as below:
+---------------------+----------------+
| Environment | compilation |
+---------------------+----------------+
| Loongnix-Server 8.3 | PASS |
+---------------------+----------------+
Loongnix-Server 8.3
Kernel: 4.19.190+
Compiler: gcc 8.3
next prev parent reply other threads:[~2024-03-02 3:08 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240301163931.107036-1-konstantin.v.ananyev@yandex.ru>
2024-03-01 16:43 ` checkpatch
2024-03-01 17:44 ` 0-day Robot
2024-03-01 21:26 ` |SUCCESS| pw137690 [PATCH] examples/l3fwd: fix Rx over not ready por dpdklab
2024-03-01 21:32 ` |FAILURE| " dpdklab
2024-03-01 21:34 ` |SUCCESS| " dpdklab
2024-03-01 21:35 ` dpdklab
2024-03-01 21:45 ` |FAILURE| " dpdklab
2024-03-01 21:48 ` |SUCCESS| " dpdklab
2024-03-01 22:03 ` dpdklab
2024-03-01 22:20 ` |FAILURE| " dpdklab
2024-03-01 22:27 ` |SUCCESS| " dpdklab
2024-03-01 22:29 ` dpdklab
2024-03-01 22:33 ` dpdklab
2024-03-01 22:36 ` dpdklab
2024-03-01 22:37 ` dpdklab
2024-03-01 22:41 ` dpdklab
2024-03-01 22:43 ` dpdklab
2024-03-01 22:49 ` dpdklab
2024-03-01 23:21 ` dpdklab
2024-03-01 23:24 ` dpdklab
2024-03-01 23:25 ` dpdklab
2024-03-01 23:27 ` |FAILURE| " dpdklab
2024-03-01 23:45 ` |SUCCESS| " dpdklab
2024-03-02 0:15 ` dpdklab
2024-03-02 0:55 ` dpdklab
2024-03-02 1:01 ` dpdklab
2024-03-02 1:01 ` dpdklab
2024-03-02 1:02 ` dpdklab
2024-03-02 1:03 ` dpdklab
2024-03-02 1:03 ` dpdklab
2024-03-02 1:03 ` dpdklab
2024-03-02 1:04 ` dpdklab
2024-03-02 1:04 ` dpdklab
2024-03-02 1:04 ` dpdklab
2024-03-02 1:05 ` dpdklab
2024-03-02 1:05 ` dpdklab
2024-03-02 1:05 ` dpdklab
2024-03-02 1:06 ` dpdklab
2024-03-02 1:06 ` dpdklab
2024-03-02 1:06 ` dpdklab
2024-03-02 1:06 ` dpdklab
2024-03-02 1:07 ` dpdklab
2024-03-02 1:07 ` dpdklab
2024-03-02 1:07 ` dpdklab
2024-03-02 1:07 ` dpdklab
2024-03-02 1:08 ` dpdklab
2024-03-02 1:08 ` dpdklab
2024-03-02 1:08 ` dpdklab
2024-03-02 1:09 ` dpdklab
2024-03-02 1:09 ` dpdklab
2024-03-02 1:09 ` dpdklab
2024-03-02 1:10 ` dpdklab
2024-03-02 1:10 ` dpdklab
2024-03-02 1:10 ` dpdklab
2024-03-02 1:11 ` dpdklab
2024-03-02 1:11 ` dpdklab
2024-03-02 1:11 ` dpdklab
2024-03-02 1:11 ` dpdklab
2024-03-02 1:12 ` dpdklab
2024-03-02 1:12 ` dpdklab
2024-03-02 1:12 ` dpdklab
2024-03-02 1:18 ` dpdklab
2024-03-02 1:20 ` dpdklab
2024-03-02 1:22 ` dpdklab
2024-03-02 1:24 ` dpdklab
2024-03-02 1:24 ` dpdklab
2024-03-02 2:25 ` dpdklab
2024-03-02 2:43 ` qemudev [this message]
2024-03-02 2:48 ` |SUCCESS| pw137690 [PATCH] examples/l3fwd: fix Rx over not ready port qemudev
2024-03-02 4:05 ` |SUCCESS| pw137690 [PATCH] examples/l3fwd: fix Rx over not ready por dpdklab
2024-03-03 1:32 ` dpdklab
2024-03-04 6:09 ` dpdklab
2024-03-05 23:55 ` dpdklab
2024-03-06 0:27 ` dpdklab
2024-03-06 1:00 ` 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=202403020243.4222hqBj3455894@localhost.localdomain \
--to=qemudev@loongson.cn \
--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).