From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124827-124828 [PATCH v3 2/2] eal: add option to put timestamp on console output
Date: Tue, 7 Mar 2023 03:16:44 +0800 [thread overview]
Message-ID: <202303061916.326JGi6J403849@localhost.localdomain> (raw)
In-Reply-To: <20230306192810.106154-3-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124828
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Mon, 6 Mar 2023 11:28:09 -0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: e0fb0051ff8f621a2b001d9243cebe50f3d42cf5
124827-124828 --> 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:[~2023-03-06 19:30 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230306192810.106154-3-stephen@networkplumber.org>
2023-03-06 19:16 ` qemudev [this message]
2023-03-06 19:20 ` qemudev
2023-03-06 19:28 ` |SUCCESS| pw124828 " checkpatch
2023-03-06 21:39 ` 0-day Robot
2023-03-06 22:23 |SUCCESS| pw124827-124828 [PATCH] [v3, " dpdklab
2023-03-06 22:24 dpdklab
2023-03-06 22:28 dpdklab
2023-03-06 22:33 dpdklab
2023-03-06 22:33 dpdklab
2023-03-06 22:35 dpdklab
2023-03-06 22:35 dpdklab
2023-03-06 22:38 dpdklab
2023-03-06 22:40 dpdklab
2023-03-06 22:43 dpdklab
2023-03-06 22:49 dpdklab
2023-03-06 23:28 dpdklab
2023-03-06 23:29 dpdklab
2023-03-06 23:37 dpdklab
2023-03-06 23:38 dpdklab
2023-03-06 23:39 dpdklab
2023-03-06 23:40 dpdklab
2023-03-06 23:41 dpdklab
2023-03-06 23:44 dpdklab
2023-03-06 23:46 dpdklab
2023-03-06 23:49 dpdklab
2023-03-06 23:52 dpdklab
2023-03-06 23:55 dpdklab
2023-03-07 0:27 dpdklab
2023-03-07 4:11 dpdklab
2023-03-07 4:17 dpdklab
2023-03-07 4:24 dpdklab
2023-03-07 4:34 dpdklab
2023-03-07 4:36 dpdklab
2023-03-07 4:37 dpdklab
2023-03-07 4:38 dpdklab
2023-03-07 4:39 dpdklab
2023-03-07 4:47 dpdklab
2023-03-07 4:47 dpdklab
2023-03-07 4:49 dpdklab
2023-03-07 4:50 dpdklab
2023-03-07 4:52 dpdklab
2023-03-07 4:58 dpdklab
2023-03-07 5:07 dpdklab
2023-03-07 5:23 dpdklab
2023-03-07 5:28 dpdklab
2023-03-07 5:37 dpdklab
2023-03-07 5:42 dpdklab
2023-03-07 5:44 dpdklab
2023-03-07 5:45 dpdklab
2023-03-07 5:50 dpdklab
2023-03-07 6:02 dpdklab
2023-03-07 6:04 dpdklab
2023-03-07 6:04 dpdklab
2023-03-07 6:04 dpdklab
2023-03-07 6:07 dpdklab
2023-03-07 6:07 dpdklab
2023-03-07 6:08 dpdklab
2023-03-07 6:09 dpdklab
2023-03-07 7:03 dpdklab
2023-03-07 7:05 dpdklab
2023-03-07 7:05 dpdklab
2023-03-07 8:01 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=202303061916.326JGi6J403849@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).