From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124306-124310 [PATCH v7 5/5] ipsec: fix usage of RTE_LOGTYPE_USER1
Date: Wed, 22 Feb 2023 02:45:37 +0800 [thread overview]
Message-ID: <202302211845.31LIjbsJ1306402@localhost.localdomain> (raw)
In-Reply-To: <20230221185553.513432-6-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124310
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tue, 21 Feb 2023 10:55:49 -0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 9bd5ebca59c865aead7096358fb733e53a72007b
124306-124310 --> 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-21 18:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230221185553.513432-6-stephen@networkplumber.org>
2023-02-21 18:45 ` qemudev [this message]
2023-02-21 18:49 ` qemudev
2023-02-21 18:56 ` |SUCCESS| pw124310 " checkpatch
2023-02-21 21:39 ` 0-day Robot
2023-02-21 19:54 |SUCCESS| pw124306-124310 [PATCH] [v7, " dpdklab
2023-02-21 19:58 dpdklab
2023-02-21 20:00 dpdklab
2023-02-21 20:00 dpdklab
2023-02-21 20:09 dpdklab
2023-02-21 20:12 dpdklab
2023-02-21 20:26 dpdklab
2023-02-21 20:33 dpdklab
2023-02-21 21:04 dpdklab
2023-02-21 21:11 dpdklab
2023-02-22 2:44 dpdklab
2023-02-22 2:53 dpdklab
2023-02-22 2:57 dpdklab
2023-02-22 2:59 dpdklab
2023-02-22 3:00 dpdklab
2023-02-22 3:08 dpdklab
2023-02-22 3:09 dpdklab
2023-02-22 3:12 dpdklab
2023-02-22 3:17 dpdklab
2023-02-22 3:22 dpdklab
2023-02-22 3:24 dpdklab
2023-02-22 3:27 dpdklab
2023-02-22 3:30 dpdklab
2023-02-22 3:30 dpdklab
2023-02-22 4:29 dpdklab
2023-02-23 18:10 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=202302211845.31LIjbsJ1306402@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).