From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125091 [PATCH v2 1/1] doc: fix cnxk platform HW accelerator blocks list
Date: Wed, 15 Mar 2023 08:50:17 +0800 [thread overview]
Message-ID: <202303150050.32F0oHRD3172527@localhost.localdomain> (raw)
In-Reply-To: <20230314064501.14876-1-syalavarthi@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125091
_Compilation OK_
Submitter: Srikanth Yalavarthi <syalavarthi@marvell.com>
Date: Mon, 13 Mar 2023 23:45:01 -0700
DPDK git baseline: Repo:dpdk-next-net-mrvl
Branch: for-next-net
CommitID: baf13c3135d0c5998fff7edc23fb89412dc89246
125091 --> 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-03-15 1:04 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230314064501.14876-1-syalavarthi@marvell.com>
2023-03-14 6:45 ` checkpatch
2023-03-14 8:59 ` 0-day Robot
2023-03-15 0:50 ` qemudev [this message]
2023-03-15 0:50 ` qemudev
2023-03-16 8:49 |SUCCESS| pw125091 [PATCH] [v2, " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-03-16 7:57 dpdklab
2023-03-15 12:35 dpdklab
2023-03-15 12:35 dpdklab
2023-03-15 11:53 dpdklab
2023-03-15 11:39 dpdklab
2023-03-15 11:37 dpdklab
2023-03-15 11:37 dpdklab
2023-03-15 11:26 dpdklab
2023-03-15 11:24 dpdklab
2023-03-15 11:20 dpdklab
2023-03-15 11:17 dpdklab
2023-03-15 11:09 dpdklab
2023-03-15 11:09 dpdklab
2023-03-15 11:05 dpdklab
2023-03-15 11:01 dpdklab
2023-03-15 10:55 dpdklab
2023-03-15 10:52 dpdklab
2023-03-15 10:50 dpdklab
2023-03-15 10:40 dpdklab
2023-03-15 10:39 dpdklab
2023-03-15 10:33 dpdklab
2023-03-15 10:33 dpdklab
2023-03-15 10:30 dpdklab
2023-03-15 10:19 dpdklab
2023-03-15 10:15 dpdklab
2023-03-15 10:14 dpdklab
2023-03-15 10:12 dpdklab
2023-03-15 9:55 dpdklab
2023-03-14 21:26 dpdklab
2023-03-14 20:43 dpdklab
2023-03-14 20:02 dpdklab
2023-03-14 19:39 dpdklab
2023-03-14 10:48 dpdklab
2023-03-14 10:17 dpdklab
2023-03-14 10:11 dpdklab
2023-03-14 10:06 dpdklab
2023-03-14 10:06 dpdklab
2023-03-14 10:05 dpdklab
2023-03-14 10:03 dpdklab
2023-03-14 10:01 dpdklab
2023-03-14 9:59 dpdklab
2023-03-14 9:59 dpdklab
2023-03-14 9:58 dpdklab
2023-03-14 9:57 dpdklab
2023-03-14 9:54 dpdklab
2023-03-14 9:51 dpdklab
2023-03-14 9:49 dpdklab
2023-03-14 9:04 dpdklab
2023-03-14 9:00 dpdklab
2023-03-14 8:54 dpdklab
2023-03-14 8:53 dpdklab
2023-03-14 8:51 dpdklab
2023-03-14 8:51 dpdklab
2023-03-14 8:49 dpdklab
2023-03-14 8:47 dpdklab
2023-03-14 8:45 dpdklab
2023-03-14 8:44 dpdklab
2023-03-14 8:43 dpdklab
2023-03-14 8:39 dpdklab
2023-03-14 8:33 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=202303150050.32F0oHRD3172527@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).