From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139478 [PATCH] doc: Fix some typos in mbuf_lib.rst and net/cnxk comments.
Date: Thu, 18 Apr 2024 13:59:21 +0800 [thread overview]
Message-ID: <202404180559.43I5xLYG1418113@localhost.localdomain> (raw)
In-Reply-To: <20240418062025.26674-1-maoyingming@baidu.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139478
_Compilation OK_
Submitter: Mao YingMing <maoyingming@baidu.com>
Date: Thu, 18 Apr 2024 14:20:25 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139478 --> 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-04-18 6:27 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240418062025.26674-1-maoyingming@baidu.com>
2024-04-18 5:59 ` qemudev [this message]
2024-04-18 6:03 ` qemudev
2024-04-18 6:23 ` checkpatch
2024-04-18 7:24 ` 0-day Robot
2024-04-18 10:53 ` |SUCCESS| pw139478 [PATCH] doc: Fix some typos in mbuf_lib.rst and n dpdklab
2024-04-18 10:59 ` dpdklab
2024-04-18 11:13 ` dpdklab
2024-04-18 11:17 ` dpdklab
2024-04-18 11:19 ` dpdklab
2024-04-18 11:20 ` dpdklab
2024-04-18 11:27 ` dpdklab
2024-04-18 11:28 ` dpdklab
2024-04-18 11:28 ` dpdklab
2024-04-18 11:28 ` dpdklab
2024-04-18 11:28 ` dpdklab
2024-04-18 11:30 ` dpdklab
2024-04-18 11:31 ` dpdklab
2024-04-18 11:39 ` dpdklab
2024-04-18 11:41 ` dpdklab
2024-04-18 11:42 ` dpdklab
2024-04-18 11:42 ` dpdklab
2024-04-18 11:43 ` dpdklab
2024-04-18 11:48 ` dpdklab
2024-04-18 11:49 ` dpdklab
2024-04-18 12:09 ` dpdklab
2024-04-18 12:10 ` dpdklab
2024-04-18 12:11 ` dpdklab
2024-04-18 12:17 ` dpdklab
2024-04-18 12:20 ` dpdklab
2024-04-18 12:21 ` dpdklab
2024-04-18 12:32 ` dpdklab
2024-04-18 12:33 ` dpdklab
2024-04-18 12:36 ` dpdklab
2024-04-18 12:37 ` dpdklab
2024-04-18 12:37 ` dpdklab
2024-04-18 12:38 ` dpdklab
2024-04-18 12:38 ` dpdklab
2024-04-18 12:38 ` dpdklab
2024-04-18 12:38 ` dpdklab
2024-04-18 12:39 ` dpdklab
2024-04-18 12:39 ` dpdklab
2024-04-18 12:39 ` dpdklab
2024-04-18 12:39 ` dpdklab
2024-04-18 12:40 ` dpdklab
2024-04-18 12:40 ` dpdklab
2024-04-18 12:41 ` dpdklab
2024-04-18 12:41 ` dpdklab
2024-04-18 12:41 ` dpdklab
2024-04-18 12:41 ` dpdklab
2024-04-18 12:41 ` dpdklab
2024-04-18 12:42 ` dpdklab
2024-04-18 12:42 ` dpdklab
2024-04-18 12:43 ` dpdklab
2024-04-18 12:45 ` dpdklab
2024-04-18 12:49 ` dpdklab
2024-04-18 12:50 ` dpdklab
2024-04-18 12:51 ` dpdklab
2024-04-18 12:51 ` dpdklab
2024-04-18 12:52 ` dpdklab
2024-04-18 12:52 ` dpdklab
2024-04-18 12:52 ` dpdklab
2024-04-18 12:53 ` dpdklab
2024-04-18 12:53 ` dpdklab
2024-04-18 12:53 ` dpdklab
2024-04-18 12:53 ` dpdklab
2024-04-18 12:53 ` dpdklab
2024-04-18 12:53 ` dpdklab
2024-04-18 12:54 ` dpdklab
2024-04-18 12:54 ` dpdklab
2024-04-18 12:54 ` dpdklab
2024-04-18 12:54 ` dpdklab
2024-04-18 12:55 ` dpdklab
2024-04-18 12:57 ` dpdklab
2024-04-18 12:58 ` dpdklab
2024-04-18 13:02 ` dpdklab
2024-04-18 13:03 ` dpdklab
2024-04-18 13:03 ` dpdklab
2024-04-18 13:04 ` dpdklab
2024-04-18 13:05 ` dpdklab
2024-04-18 13:40 ` dpdklab
2024-04-18 13:59 ` dpdklab
2024-04-18 14:01 ` dpdklab
2024-04-18 14:04 ` dpdklab
2024-04-18 14:24 ` dpdklab
2024-04-18 14:57 ` dpdklab
2024-04-18 15:17 ` dpdklab
2024-04-18 15:21 ` dpdklab
2024-04-18 15:26 ` dpdklab
2024-04-18 15:30 ` dpdklab
2024-04-18 15:49 ` dpdklab
2024-04-18 17:05 ` dpdklab
2024-04-18 17:20 ` 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=202404180559.43I5xLYG1418113@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).