From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw130511-130512 [PATCH 2/2] doc: update security guide
Date: Fri, 18 Aug 2023 17:31:28 +0800 [thread overview]
Message-ID: <202308180931.37I9VSVW3710557@localhost.localdomain> (raw)
In-Reply-To: <20230818092943.1771-2-anoobj@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/130512
_Compilation OK_
Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Fri, 18 Aug 2023 14:59:42 +0530
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 9836014d4c2b1b2c29948c928fd386b2944b6bcf
130511-130512 --> 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-08-18 9:45 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230818092943.1771-2-anoobj@marvell.com>
2023-08-18 9:30 ` |SUCCESS| pw130512 " checkpatch
2023-08-18 9:31 ` qemudev [this message]
2023-08-18 9:35 ` |SUCCESS| pw130511-130512 " qemudev
2023-08-18 20:19 ` |SUCCESS| pw130512 " 0-day Robot
2023-08-18 15:57 |SUCCESS| pw130511-130512 [PATCH] [2/2] " dpdklab
2023-08-18 15:59 dpdklab
2023-08-18 16:15 dpdklab
2023-08-18 16:15 dpdklab
2023-08-18 16:47 dpdklab
2023-08-18 16:48 dpdklab
2023-08-18 16:48 dpdklab
2023-08-18 16:48 dpdklab
2023-08-18 16:48 dpdklab
2023-08-18 16:49 dpdklab
2023-08-18 16:49 dpdklab
2023-08-18 16:49 dpdklab
2023-08-18 16:50 dpdklab
2023-08-18 16:50 dpdklab
2023-08-18 16:50 dpdklab
2023-08-18 16:50 dpdklab
2023-08-18 16:51 dpdklab
2023-08-18 16:52 dpdklab
2023-08-18 16:52 dpdklab
2023-08-18 16:53 dpdklab
2023-08-18 16:54 dpdklab
2023-08-18 16:58 dpdklab
2023-08-18 17:08 dpdklab
2023-08-18 17:12 dpdklab
2023-08-18 17:26 dpdklab
2023-08-18 17:29 dpdklab
2023-08-18 17:30 dpdklab
2023-08-18 17:32 dpdklab
2023-08-18 17:33 dpdklab
2023-08-18 17:37 dpdklab
2023-08-18 17:37 dpdklab
2023-08-18 17:40 dpdklab
2023-08-18 17:42 dpdklab
2023-08-18 17:45 dpdklab
2023-08-18 17:45 dpdklab
2023-08-18 17:49 dpdklab
2023-08-18 17:56 dpdklab
2023-08-18 18:05 dpdklab
2023-08-18 18:07 dpdklab
2023-08-18 18:12 dpdklab
2023-08-18 18:16 dpdklab
2023-08-18 18:17 dpdklab
2023-08-18 18:23 dpdklab
2023-08-18 18:24 dpdklab
2023-08-18 18:27 dpdklab
2023-08-18 18:44 dpdklab
2023-08-18 18:44 dpdklab
2023-08-18 18:45 dpdklab
2023-08-18 18:48 dpdklab
2023-08-18 18:50 dpdklab
2023-08-18 18:52 dpdklab
2023-08-18 19:00 dpdklab
2023-08-18 19:12 dpdklab
2023-08-19 4:15 dpdklab
2023-08-19 4:32 dpdklab
2023-08-19 4:53 dpdklab
2023-08-19 4:57 dpdklab
2023-08-19 5:14 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=202308180931.37I9VSVW3710557@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).