From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124802 [PATCH v2] log: add timestamp for log
Date: Mon, 6 Mar 2023 15:01:57 +0800 [thread overview]
Message-ID: <202303060701.32671vxN3956202@localhost.localdomain> (raw)
In-Reply-To: <20230304040246.319-1-luzhipeng@cestc.cn>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124802
_Compilation OK_
Submitter: luzhipeng <luzhipeng@cestc.cn>
Date: Sat, 4 Mar 2023 12:02:46 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 4ef69b2877a24ddb89afaf4bb6f4e73bb52a605b
124802 --> 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:15 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230304040246.319-1-luzhipeng@cestc.cn>
2023-03-04 4:03 ` |WARNING| " checkpatch
2023-03-04 5:59 ` |SUCCESS| " 0-day Robot
2023-03-06 7:01 ` qemudev [this message]
2023-03-06 7:02 ` qemudev
2023-03-04 6:10 |SUCCESS| pw124802 [PATCH] [v2] " dpdklab
2023-03-04 6:15 dpdklab
2023-03-04 6:20 dpdklab
2023-03-04 6:22 dpdklab
2023-03-04 6:24 dpdklab
2023-03-04 6:26 dpdklab
2023-03-04 6:28 dpdklab
2023-03-04 6:28 dpdklab
2023-03-04 6:36 dpdklab
2023-03-04 6:41 dpdklab
2023-03-04 7:18 dpdklab
2023-03-04 7:23 dpdklab
2023-03-04 7:23 dpdklab
2023-03-04 7:24 dpdklab
2023-03-04 7:25 dpdklab
2023-03-04 7:28 dpdklab
2023-03-04 7:31 dpdklab
2023-03-04 7:34 dpdklab
2023-03-04 7:35 dpdklab
2023-03-04 7:40 dpdklab
2023-03-04 7:43 dpdklab
2023-03-04 7:56 dpdklab
2023-03-04 8:36 dpdklab
2023-03-04 10:01 dpdklab
2023-03-04 14:30 dpdklab
2023-03-04 15:23 dpdklab
2023-03-04 23:05 dpdklab
2023-03-05 0:38 dpdklab
2023-03-05 13:51 dpdklab
2023-03-05 13:57 dpdklab
2023-03-05 14:06 dpdklab
2023-03-05 14:06 dpdklab
2023-03-05 14:08 dpdklab
2023-03-05 14:09 dpdklab
2023-03-05 14:11 dpdklab
2023-03-05 14:11 dpdklab
2023-03-05 14:14 dpdklab
2023-03-05 14:15 dpdklab
2023-03-05 14:16 dpdklab
2023-03-05 14:18 dpdklab
2023-03-05 14:20 dpdklab
2023-03-05 14:21 dpdklab
2023-03-05 14:21 dpdklab
2023-03-05 14:44 dpdklab
2023-03-05 14:45 dpdklab
2023-03-05 14:48 dpdklab
2023-03-05 14:52 dpdklab
2023-03-05 14:53 dpdklab
2023-03-05 14:56 dpdklab
2023-03-05 14:59 dpdklab
2023-03-05 15:08 dpdklab
2023-03-05 15:09 dpdklab
2023-03-05 15:09 dpdklab
2023-03-06 4:10 dpdklab
2023-03-06 4:13 dpdklab
2023-03-06 4:17 dpdklab
2023-03-06 4:29 dpdklab
2023-03-06 4:32 dpdklab
2023-03-06 4:36 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=202303060701.32671vxN3956202@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).