From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124079-124081 [PATCH 3/3] examples/ipsec-secgw: refactor inline capability check
Date: Thu, 16 Feb 2023 22:15:14 +0800 [thread overview]
Message-ID: <202302161415.31GEFE041625221@localhost.localdomain> (raw)
In-Reply-To: <20230216142442.3657742-3-gakhil@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124081
_Compilation OK_
Submitter: Akhil Goyal <gakhil@marvell.com>
Date: Thu, 16 Feb 2023 19:54:40 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 8a3ef4b89e6dd0247355fdf3a77ff7ec1db28d8d
124079-124081 --> 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-16 14:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230216142442.3657742-3-gakhil@marvell.com>
2023-02-16 14:15 ` qemudev [this message]
2023-02-16 14:19 ` qemudev
2023-02-16 14:25 ` |SUCCESS| pw124081 " checkpatch
2023-02-16 16:40 ` 0-day Robot
2023-02-16 14:53 |SUCCESS| pw124079-124081 [PATCH] [3/3] " dpdklab
2023-02-16 14:55 dpdklab
2023-02-16 14:58 dpdklab
2023-02-16 15:04 dpdklab
2023-02-16 15:05 dpdklab
2023-02-16 15:12 dpdklab
2023-02-16 18:26 dpdklab
2023-02-16 18:29 dpdklab
2023-02-16 18:44 dpdklab
2023-02-16 18:47 dpdklab
2023-02-16 18:48 dpdklab
2023-02-16 18:49 dpdklab
2023-02-16 18:52 dpdklab
2023-02-16 18:53 dpdklab
2023-02-16 18:54 dpdklab
2023-02-16 18:55 dpdklab
2023-02-16 19:00 dpdklab
2023-02-16 19:03 dpdklab
2023-02-16 19:10 dpdklab
2023-02-16 19:10 dpdklab
2023-02-18 1:06 dpdklab
2023-02-19 11:33 dpdklab
2023-02-24 23:11 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=202302161415.31GEFE041625221@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).