From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122219-122223 [PATCH v1 6/6] doc: updated naming convention for acc200 PMD
Date: Wed, 18 Jan 2023 07:03:43 +0800 [thread overview]
Message-ID: <202301172303.30HN3hMh1951399@localhost.localdomain> (raw)
In-Reply-To: <20230117223642.17618-7-nicolas.chautru@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/122223
_Compilation OK_
Submitter: Nicolas Chautru <nicolas.chautru@intel.com>
Date: Tue, 17 Jan 2023 22:36:37 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 83397b9f073904438965e1fda2efe76f7850fe01
122219-122223 --> 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:[~2023-01-17 23:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230117223642.17618-7-nicolas.chautru@intel.com>
2023-01-17 22:41 ` |WARNING| pw122223 " checkpatch
2023-01-17 23:03 ` qemudev [this message]
2023-01-17 23:07 ` |SUCCESS| pw122219-122223 " qemudev
2023-01-17 23:39 ` |FAILURE| pw122223 " 0-day Robot
2023-01-18 3:06 |SUCCESS| pw122219-122223 [PATCH] [v1, " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-01-18 2:17 dpdklab
2023-01-18 1:48 dpdklab
2023-01-18 1:18 dpdklab
2023-01-18 1:18 dpdklab
2023-01-18 1:13 dpdklab
2023-01-18 1:12 dpdklab
2023-01-18 1:12 dpdklab
2023-01-18 1:12 dpdklab
2023-01-18 1:12 dpdklab
2023-01-18 1:12 dpdklab
2023-01-18 1:12 dpdklab
2023-01-18 1:12 dpdklab
2023-01-17 23:30 dpdklab
2023-01-17 23:25 dpdklab
2023-01-17 23:23 dpdklab
2023-01-17 23:19 dpdklab
2023-01-17 23:16 dpdklab
2023-01-17 23:15 dpdklab
2023-01-17 23:11 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=202301172303.30HN3hMh1951399@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).