From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122478 [PATCH v2] mailmap: update contributor entry
Date: Wed, 25 Jan 2023 09:45:25 +0800 [thread overview]
Message-ID: <202301250145.30P1jPwR541331@localhost.localdomain> (raw)
In-Reply-To: <20230124130110.19666-1-viacheslav.galaktionov@arknetworks.am>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/122478
_Compilation OK_
Submitter: Viacheslav Galaktionov <Viacheslav.Galaktionov@arknetworks.am>
Date: Tue, 24 Jan 2023 17:01:10 +0400
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 2a211079a92e962bbd0ec81e425a6ffc32890e67
122478 --> 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-01-25 1:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230124130110.19666-1-viacheslav.galaktionov@arknetworks.am>
2023-01-24 13:03 ` |WARNING| " checkpatch
2023-01-24 13:59 ` |SUCCESS| " 0-day Robot
2023-01-25 1:45 ` qemudev [this message]
2023-01-25 1:49 ` qemudev
2023-01-25 13:09 |SUCCESS| pw122478 [PATCH] [v2] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-01-25 1:23 dpdklab
2023-01-25 1:02 dpdklab
2023-01-24 23:33 dpdklab
2023-01-24 22:14 dpdklab
2023-01-24 22:03 dpdklab
2023-01-24 21:13 dpdklab
2023-01-24 21:12 dpdklab
2023-01-24 21:12 dpdklab
2023-01-24 21:11 dpdklab
2023-01-24 21:11 dpdklab
2023-01-24 21:11 dpdklab
2023-01-24 21:11 dpdklab
2023-01-24 21:11 dpdklab
2023-01-24 21:11 dpdklab
2023-01-24 20:33 dpdklab
2023-01-24 20:18 dpdklab
2023-01-24 19:36 dpdklab
2023-01-24 14:12 dpdklab
2023-01-24 13:31 dpdklab
2023-01-24 13:31 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=202301250145.30P1jPwR541331@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).