From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124212-124216 [PATCH v6 5/5] ipsec: fix usage of RTE_LOGTYPE_USER1
Date: Tue, 21 Feb 2023 02:40:30 +0800 [thread overview]
Message-ID: <202302201840.31KIeUWu3916737@localhost.localdomain> (raw)
In-Reply-To: <20230220185001.50714-6-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124216
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Mon, 20 Feb 2023 10:49:57 -0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 9bd5ebca59c865aead7096358fb733e53a72007b
124212-124216 --> 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-02-20 18:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230220185001.50714-6-stephen@networkplumber.org>
2023-02-20 18:40 ` qemudev [this message]
2023-02-20 18:44 ` qemudev
2023-02-20 18:50 ` |SUCCESS| pw124216 " checkpatch
2023-02-20 20:59 ` 0-day Robot
2023-02-20 19:18 |SUCCESS| pw124212-124216 [PATCH] [v6, " dpdklab
2023-02-20 19:22 dpdklab
2023-02-20 19:22 dpdklab
2023-02-20 19:28 dpdklab
2023-02-20 19:30 dpdklab
2023-02-20 19:33 dpdklab
2023-02-20 19:33 dpdklab
2023-02-20 19:34 dpdklab
2023-02-20 19:37 dpdklab
2023-02-20 19:41 dpdklab
2023-02-20 22:20 dpdklab
2023-02-20 22:23 dpdklab
2023-02-20 22:39 dpdklab
2023-02-20 22:44 dpdklab
2023-02-20 22:47 dpdklab
2023-02-20 22:49 dpdklab
2023-02-20 22:54 dpdklab
2023-02-20 22:59 dpdklab
2023-02-20 23:02 dpdklab
2023-02-20 23:05 dpdklab
2023-02-20 23:07 dpdklab
2023-02-20 23:10 dpdklab
2023-02-20 23:10 dpdklab
2023-02-20 23:10 dpdklab
2023-02-21 2:06 dpdklab
2023-02-22 0:06 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=202302201840.31KIeUWu3916737@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).