From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138673-138685 [PATCH v6 14/14] examples/ipsec-secgw: fix port ID restriction
Date: Fri, 22 Mar 2024 02:28:17 +0800 [thread overview]
Message-ID: <202403211828.42LISHec995871@localhost.localdomain> (raw)
In-Reply-To: <20240321184721.69040-15-sivaprasad.tummala@amd.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138685
_Compilation OK_
Submitter: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Date: Thu, 21 Mar 2024 19:47:07 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: c96e9ca312d9b32637bbdcfbfc1bca93a8629faa
138673-138685 --> 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:[~2024-03-21 18:53 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240321184721.69040-15-sivaprasad.tummala@amd.com>
2024-03-21 18:28 ` qemudev [this message]
2024-03-21 18:32 ` qemudev
2024-03-21 18:51 ` |SUCCESS| pw138685 " checkpatch
2024-03-21 19:32 ` |SUCCESS| pw138673-138685 [PATCH] [v6,14/14] examples/ipsec-secgw: f dpdklab
2024-03-21 19:32 ` dpdklab
2024-03-21 19:33 ` dpdklab
2024-03-21 19:33 ` dpdklab
2024-03-21 19:34 ` dpdklab
2024-03-21 19:34 ` dpdklab
2024-03-21 19:34 ` dpdklab
2024-03-21 19:41 ` dpdklab
2024-03-21 19:41 ` dpdklab
2024-03-21 19:41 ` dpdklab
2024-03-21 19:42 ` dpdklab
2024-03-21 19:42 ` dpdklab
2024-03-21 19:42 ` dpdklab
2024-03-21 19:43 ` dpdklab
2024-03-21 19:43 ` dpdklab
2024-03-21 19:43 ` dpdklab
2024-03-21 19:43 ` dpdklab
2024-03-21 19:43 ` dpdklab
2024-03-21 19:43 ` dpdklab
2024-03-21 19:44 ` dpdklab
2024-03-21 19:44 ` dpdklab
2024-03-21 19:44 ` dpdklab
2024-03-21 19:44 ` |SUCCESS| pw138685 [PATCH v6 14/14] examples/ipsec-secgw: fix port ID restriction 0-day Robot
2024-03-21 19:45 ` |SUCCESS| pw138673-138685 [PATCH] [v6,14/14] examples/ipsec-secgw: f dpdklab
2024-03-21 19:45 ` dpdklab
2024-03-21 19:46 ` dpdklab
2024-03-21 19:47 ` dpdklab
2024-03-21 19:48 ` dpdklab
2024-03-21 19:48 ` dpdklab
2024-03-21 19:48 ` dpdklab
2024-03-21 19:48 ` dpdklab
2024-03-21 19:48 ` dpdklab
2024-03-21 19:49 ` dpdklab
2024-03-21 19:49 ` dpdklab
2024-03-21 19:49 ` dpdklab
2024-03-21 19:51 ` dpdklab
2024-03-21 19:52 ` dpdklab
2024-03-21 19:53 ` dpdklab
2024-03-21 19:53 ` dpdklab
2024-03-21 19:54 ` dpdklab
2024-03-21 19:54 ` dpdklab
2024-03-21 19:54 ` dpdklab
2024-03-21 19:54 ` dpdklab
2024-03-21 19:54 ` dpdklab
2024-03-21 19:55 ` dpdklab
2024-03-21 19:55 ` dpdklab
2024-03-21 19:55 ` dpdklab
2024-03-21 19:56 ` dpdklab
2024-03-21 20:00 ` dpdklab
2024-03-21 20:00 ` dpdklab
2024-03-21 20:01 ` dpdklab
2024-03-21 20:01 ` dpdklab
2024-03-21 20:01 ` dpdklab
2024-03-21 20:01 ` dpdklab
2024-03-21 20:01 ` dpdklab
2024-03-21 20:02 ` dpdklab
2024-03-21 20:02 ` dpdklab
2024-03-21 20:02 ` dpdklab
2024-03-21 20:02 ` dpdklab
2024-03-21 20:02 ` dpdklab
2024-03-21 20:02 ` dpdklab
2024-03-21 20:03 ` dpdklab
2024-03-21 20:03 ` dpdklab
2024-03-21 20:06 ` dpdklab
2024-03-21 20:08 ` dpdklab
2024-03-21 20:08 ` dpdklab
2024-03-21 20:10 ` dpdklab
2024-03-21 20:10 ` dpdklab
2024-03-21 20:16 ` dpdklab
2024-03-21 20:34 ` dpdklab
2024-03-21 21:19 ` dpdklab
2024-03-22 2:34 ` dpdklab
2024-03-23 11:06 ` dpdklab
2024-03-23 11:43 ` 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=202403211828.42LISHec995871@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).