From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139176 [PATCH v3] cnxk: disable building template files
Date: Sat, 6 Apr 2024 05:24:59 +0800 [thread overview]
Message-ID: <202404052124.435LOxpF3378647@localhost.localdomain> (raw)
In-Reply-To: <20240405214742.8324-1-pbhagavatula@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139176
_Compilation OK_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Sat, 6 Apr 2024 03:17:41 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139176 --> 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-04-05 21:49 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240405214742.8324-1-pbhagavatula@marvell.com>
2024-04-05 21:24 ` qemudev [this message]
2024-04-05 21:29 ` qemudev
2024-04-05 21:49 ` checkpatch
2024-04-05 22:44 ` 0-day Robot
2024-04-06 11:59 ` |SUCCESS| pw139176 [PATCH] [v3] cnxk: disable building template file dpdklab
2024-04-06 12:06 ` dpdklab
2024-04-06 12:07 ` dpdklab
2024-04-06 12:07 ` dpdklab
2024-04-06 12:11 ` dpdklab
2024-04-06 12:31 ` dpdklab
2024-04-06 12:32 ` dpdklab
2024-04-06 12:33 ` dpdklab
2024-04-06 12:34 ` dpdklab
2024-04-06 12:36 ` dpdklab
2024-04-06 12:36 ` dpdklab
2024-04-06 12:38 ` dpdklab
2024-04-06 12:38 ` dpdklab
2024-04-06 12:38 ` dpdklab
2024-04-06 12:39 ` dpdklab
2024-04-06 12:39 ` dpdklab
2024-04-06 12:43 ` dpdklab
2024-04-06 12:43 ` dpdklab
2024-04-06 12:43 ` dpdklab
2024-04-06 12:44 ` dpdklab
2024-04-06 12:48 ` dpdklab
2024-04-06 12:50 ` dpdklab
2024-04-06 12:50 ` dpdklab
2024-04-06 12:50 ` dpdklab
2024-04-06 12:51 ` dpdklab
2024-04-06 12:51 ` dpdklab
2024-04-06 12:52 ` dpdklab
2024-04-06 13:17 ` dpdklab
2024-04-06 13:21 ` dpdklab
2024-04-06 13:21 ` dpdklab
2024-04-06 13:22 ` dpdklab
2024-04-06 13:22 ` dpdklab
2024-04-06 13:24 ` dpdklab
2024-04-06 13:26 ` dpdklab
2024-04-06 13:26 ` dpdklab
2024-04-06 13:26 ` dpdklab
2024-04-06 13:27 ` dpdklab
2024-04-06 13:27 ` dpdklab
2024-04-06 13:29 ` dpdklab
2024-04-06 13:30 ` dpdklab
2024-04-06 13:32 ` dpdklab
2024-04-06 13:33 ` dpdklab
2024-04-06 13:36 ` dpdklab
2024-04-06 13:38 ` dpdklab
2024-04-06 13:38 ` dpdklab
2024-04-06 13:38 ` dpdklab
2024-04-06 13:39 ` dpdklab
2024-04-06 13:40 ` dpdklab
2024-04-06 13:40 ` dpdklab
2024-04-06 13:40 ` dpdklab
2024-04-06 13:40 ` dpdklab
2024-04-06 13:40 ` dpdklab
2024-04-06 13:41 ` dpdklab
2024-04-06 13:41 ` dpdklab
2024-04-06 13:42 ` dpdklab
2024-04-06 13:43 ` dpdklab
2024-04-06 13:43 ` dpdklab
2024-04-06 13:44 ` dpdklab
2024-04-06 13:44 ` dpdklab
2024-04-06 13:44 ` dpdklab
2024-04-06 13:46 ` dpdklab
2024-04-06 13:47 ` dpdklab
2024-04-06 13:47 ` dpdklab
2024-04-06 13:47 ` dpdklab
2024-04-06 13:49 ` dpdklab
2024-04-06 13:51 ` dpdklab
2024-04-06 13:52 ` dpdklab
2024-04-06 13:54 ` dpdklab
2024-04-06 13:55 ` dpdklab
2024-04-06 13:57 ` dpdklab
2024-04-06 13:59 ` dpdklab
2024-04-06 13:59 ` dpdklab
2024-04-06 13:59 ` dpdklab
2024-04-06 14:00 ` dpdklab
2024-04-06 14:01 ` dpdklab
2024-04-06 14:08 ` dpdklab
2024-04-06 14:08 ` dpdklab
2024-04-06 14:08 ` dpdklab
2024-04-06 14:08 ` dpdklab
2024-04-06 14:09 ` |FAILURE| " dpdklab
2024-04-06 14:12 ` |SUCCESS| " dpdklab
2024-04-06 14:20 ` dpdklab
2024-04-06 14:20 ` |FAILURE| " dpdklab
2024-04-06 14:20 ` |SUCCESS| " dpdklab
2024-04-06 14:23 ` dpdklab
2024-04-06 14:31 ` dpdklab
2024-04-06 14:40 ` dpdklab
2024-04-06 14:40 ` 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=202404052124.435LOxpF3378647@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).