From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw128597 [PATCH] mailmap: update contributor entry
Date: Tue, 13 Jun 2023 21:52:54 +0800 [thread overview]
Message-ID: <202306131352.35DDqso31611382@localhost.localdomain> (raw)
In-Reply-To: <20230613140353.6836-1-ivan.malov@arknetworks.am>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/128597
_Compilation OK_
Submitter: Ivan Malov <ivan.malov@arknetworks.am>
Date: Tue, 13 Jun 2023 18:03:53 +0400
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 050de60d8a5cef8b7c10b4471905ca8bf69d670e
128597 --> 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-06-13 14:07 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230613140353.6836-1-ivan.malov@arknetworks.am>
2023-06-13 13:52 ` qemudev [this message]
2023-06-13 13:56 ` qemudev
2023-06-13 14:05 ` |WARNING| " checkpatch
2023-06-13 15:19 ` |SUCCESS| " 0-day Robot
2023-06-15 3:56 dpdklab
2023-06-15 4:01 dpdklab
2023-06-15 4:02 dpdklab
2023-06-15 4:02 dpdklab
2023-06-15 4:05 dpdklab
2023-06-15 4:14 dpdklab
2023-06-15 4:39 dpdklab
2023-06-15 4:48 dpdklab
2023-06-15 4:51 dpdklab
2023-06-15 4:57 dpdklab
2023-06-15 5:01 dpdklab
2023-06-15 5:04 dpdklab
2023-06-15 5:08 dpdklab
2023-06-15 5:08 dpdklab
2023-06-15 5:12 dpdklab
2023-06-15 5:12 dpdklab
2023-06-15 5:17 dpdklab
2023-06-15 5:25 dpdklab
2023-06-15 9:09 dpdklab
2023-06-15 11:07 dpdklab
2023-06-15 16:01 dpdklab
2023-06-15 16:01 dpdklab
2023-06-15 22:44 dpdklab
2023-06-15 23:00 dpdklab
2023-06-15 23:04 dpdklab
2023-06-15 23:10 dpdklab
2023-06-15 23:20 dpdklab
2023-06-16 22:38 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=202306131352.35DDqso31611382@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).