From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw128096-128098 [PATCH 3/3] app/test: test inline reassembly with multi seg
Date: Mon, 5 Jun 2023 16:10:31 +0800 [thread overview]
Message-ID: <202306050810.3558AV6L3237639@localhost.localdomain> (raw)
In-Reply-To: <20230605082122.422934-3-ndabilpuram@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/128098
_Compilation OK_
Submitter: Nithin Dabilpuram <ndabilpuram@marvell.com>
Date: Mon, 5 Jun 2023 13:51:20 +0530
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: ea71e5c0d77a75ec10b4808fc6568c3baaf94488
128096-128098 --> 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-06-05 8:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230605082122.422934-3-ndabilpuram@marvell.com>
2023-06-05 8:10 ` qemudev [this message]
2023-06-05 8:14 ` qemudev
2023-06-05 8:22 ` |SUCCESS| pw128098 " checkpatch
2023-06-05 9:19 ` 0-day Robot
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=202306050810.3558AV6L3237639@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).