From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124804 [PATCH] app/test: fix data length of each packet segment
Date: Mon, 6 Mar 2023 14:59:49 +0800 [thread overview]
Message-ID: <202303060659.3266xnTn3955983@localhost.localdomain> (raw)
In-Reply-To: <20230305203351.13599-1-zobin1999@gmail.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124804
_Compilation OK_
Submitter: Zhuobin Huang <zobin1999@gmail.com>
Date: Mon, 6 Mar 2023 04:33:51 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 4ef69b2877a24ddb89afaf4bb6f4e73bb52a605b
124804 --> 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-03-06 7:13 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230305203351.13599-1-zobin1999@gmail.com>
2023-03-05 20:35 ` |WARNING| " checkpatch
2023-03-06 6:59 ` qemudev [this message]
2023-03-06 7:00 ` |SUCCESS| " qemudev
2023-03-06 5:48 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-03-06 5:44 dpdklab
2023-03-05 22:48 dpdklab
2023-03-05 22:48 dpdklab
2023-03-05 22:45 dpdklab
2023-03-05 22:43 dpdklab
2023-03-05 22:42 dpdklab
2023-03-05 22:28 dpdklab
2023-03-05 22:28 dpdklab
2023-03-05 22:24 dpdklab
2023-03-05 22:23 dpdklab
2023-03-05 22:22 dpdklab
2023-03-05 22:21 dpdklab
2023-03-05 22:17 dpdklab
2023-03-05 22:16 dpdklab
2023-03-05 22:15 dpdklab
2023-03-05 22:13 dpdklab
2023-03-05 21:55 dpdklab
2023-03-05 21:51 dpdklab
2023-03-05 21:37 dpdklab
2023-03-05 21:22 dpdklab
2023-03-05 21:16 dpdklab
2023-03-05 21:13 dpdklab
2023-03-05 21:13 dpdklab
2023-03-05 21:07 dpdklab
2023-03-05 21:06 dpdklab
2023-03-05 21:05 dpdklab
2023-03-05 21:05 dpdklab
2023-03-05 20:59 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=202303060659.3266xnTn3955983@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).