From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw143119 [PATCH] doc: add new driver guidelines
Date: Wed, 14 Aug 2024 03:45:43 +0800 [thread overview]
Message-ID: <202408131945.47DJjh831583883@localhost.localdomain> (raw)
In-Reply-To: <20240813201250.9383-1-nandinipersad361@gmail.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/143119
_Compilation OK_
Submitter: Nandini Persad <nandinipersad361@gmail.com>
Date: Tue, 13 Aug 2024 13:12:50 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: cb9187bc5c2b4bab0ad80194ac3b60491de14e8c
143119 --> 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 parent reply other threads:[~2024-08-13 20:14 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240813201250.9383-1-nandinipersad361@gmail.com>
2024-08-13 19:45 ` qemudev [this message]
2024-08-13 19:50 ` qemudev
2024-08-13 20:13 ` |WARNING| " checkpatch
2024-08-13 20:43 ` |SUCCESS| " dpdklab
2024-08-13 20:44 ` |PENDING| " dpdklab
2024-08-13 20:45 ` dpdklab
2024-08-13 20:46 ` dpdklab
2024-08-13 20:48 ` |SUCCESS| " dpdklab
2024-08-13 20:49 ` |PENDING| " dpdklab
2024-08-13 20:50 ` dpdklab
2024-08-13 20:50 ` dpdklab
2024-08-13 20:51 ` dpdklab
2024-08-13 20:51 ` dpdklab
2024-08-13 20:54 ` |SUCCESS| " dpdklab
2024-08-13 20:55 ` |PENDING| " dpdklab
2024-08-13 20:58 ` |SUCCESS| " dpdklab
2024-08-13 20:58 ` |PENDING| " dpdklab
2024-08-13 20:58 ` |SUCCESS| " dpdklab
2024-08-13 20:58 ` |PENDING| " dpdklab
2024-08-13 20:59 ` dpdklab
2024-08-13 21:00 ` dpdklab
2024-08-13 21:02 ` |FAILURE| " 0-day Robot
2024-08-13 21:03 ` |SUCCESS| " dpdklab
2024-08-13 21:03 ` |PENDING| " dpdklab
2024-08-13 21:04 ` dpdklab
2024-08-13 21:05 ` dpdklab
2024-08-13 21:05 ` dpdklab
2024-08-13 21:05 ` dpdklab
2024-08-13 21:06 ` dpdklab
2024-08-13 21:07 ` dpdklab
2024-08-13 21:07 ` dpdklab
2024-08-13 21:07 ` dpdklab
2024-08-13 21:08 ` |SUCCESS| " dpdklab
2024-08-13 21:08 ` |PENDING| " dpdklab
2024-08-13 21:08 ` dpdklab
2024-08-13 21:09 ` dpdklab
2024-08-13 21:09 ` dpdklab
2024-08-13 21:09 ` dpdklab
2024-08-13 21:10 ` dpdklab
2024-08-13 21:11 ` |SUCCESS| " dpdklab
2024-08-13 21:11 ` |PENDING| " dpdklab
2024-08-13 21:11 ` dpdklab
2024-08-13 21:12 ` dpdklab
2024-08-13 21:12 ` |SUCCESS| " dpdklab
2024-08-13 21:13 ` |PENDING| " dpdklab
2024-08-13 21:13 ` dpdklab
2024-08-13 21:13 ` dpdklab
2024-08-13 21:13 ` dpdklab
2024-08-13 21:13 ` dpdklab
2024-08-13 21:13 ` dpdklab
2024-08-13 21:13 ` dpdklab
2024-08-13 21:14 ` dpdklab
2024-08-13 21:14 ` dpdklab
2024-08-13 21:14 ` dpdklab
2024-08-13 21:14 ` dpdklab
2024-08-13 21:15 ` dpdklab
2024-08-13 21:15 ` dpdklab
2024-08-13 21:15 ` dpdklab
2024-08-13 21:15 ` dpdklab
2024-08-13 21:16 ` |SUCCESS| " dpdklab
2024-08-13 21:16 ` dpdklab
2024-08-13 21:16 ` |PENDING| " dpdklab
2024-08-13 21:17 ` dpdklab
2024-08-13 21:17 ` dpdklab
2024-08-13 21:17 ` |SUCCESS| " dpdklab
2024-08-13 21:18 ` |PENDING| " dpdklab
2024-08-13 21:18 ` dpdklab
2024-08-13 21:18 ` dpdklab
2024-08-13 21:19 ` dpdklab
2024-08-13 21:20 ` dpdklab
2024-08-13 21:21 ` dpdklab
2024-08-13 21:21 ` dpdklab
2024-08-13 21:22 ` dpdklab
2024-08-13 21:23 ` dpdklab
2024-08-13 21:23 ` |SUCCESS| " dpdklab
2024-08-13 21:24 ` |PENDING| " dpdklab
2024-08-13 21:24 ` dpdklab
2024-08-13 21:26 ` dpdklab
2024-08-13 21:26 ` dpdklab
2024-08-13 21:27 ` dpdklab
2024-08-13 21:27 ` |SUCCESS| " dpdklab
2024-08-13 21:28 ` dpdklab
2024-08-13 21:29 ` |PENDING| " dpdklab
2024-08-13 21:32 ` |SUCCESS| " dpdklab
2024-08-13 21:34 ` dpdklab
2024-08-13 21:36 ` dpdklab
2024-08-13 21:36 ` dpdklab
2024-08-13 21:38 ` dpdklab
2024-08-13 21:42 ` dpdklab
2024-08-13 22:23 ` |PENDING| " dpdklab
2024-08-13 22:26 ` dpdklab
2024-08-13 22:28 ` |SUCCESS| " 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=202408131945.47DJjh831583883@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).