From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124891-124892 [RFC 2/2] test/security: add unittest for inline ingress oop
Date: Thu, 9 Mar 2023 16:46:54 +0800 [thread overview]
Message-ID: <202303090846.3298ksR01962362@localhost.localdomain> (raw)
In-Reply-To: <20230309085645.1630826-2-ndabilpuram@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124892
_Compilation OK_
Submitter: Nithin Dabilpuram <ndabilpuram@marvell.com>
Date: Thu, 9 Mar 2023 14:26:43 +0530
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 5028f207a4fa6d5cdd86019e43d2e2d80fa21ced
124891-124892 --> 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-03-09 9:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230309085645.1630826-2-ndabilpuram@marvell.com>
2023-03-09 8:46 ` qemudev [this message]
2023-03-09 8:50 ` qemudev
2023-03-09 8:57 ` |SUCCESS| pw124892 " checkpatch
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=202303090846.3298ksR01962362@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).