From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138748 [PATCH] table: remove experimental CRC API for some arches
Date: Fri, 22 Mar 2024 21:31:28 +0800 [thread overview]
Message-ID: <202403221331.42MDVS7V1787505@localhost.localdomain> (raw)
In-Reply-To: <20240322135328.393562-1-david.marchand@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138748
_Compilation OK_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Fri, 22 Mar 2024 14:53:28 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 0219d467bcb1d19b386b5bae8eecd3514ba13fdb
138748 --> 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-03-22 13:56 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240322135328.393562-1-david.marchand@redhat.com>
2024-03-22 13:31 ` qemudev [this message]
2024-03-22 13:35 ` qemudev
2024-03-22 13:55 ` checkpatch
2024-03-22 14:45 ` 0-day Robot
2024-03-22 17:43 ` |SUCCESS| pw138748 [PATCH] table: remove experimental CRC API for so dpdklab
2024-03-22 17:51 ` dpdklab
2024-03-22 17:51 ` dpdklab
2024-03-22 17:51 ` dpdklab
2024-03-22 17:54 ` dpdklab
2024-03-22 17:59 ` dpdklab
2024-03-22 18:01 ` dpdklab
2024-03-22 18:01 ` dpdklab
2024-03-22 18:06 ` dpdklab
2024-03-22 18:07 ` dpdklab
2024-03-22 18:08 ` dpdklab
2024-03-22 18:09 ` dpdklab
2024-03-22 18:09 ` dpdklab
2024-03-22 18:09 ` dpdklab
2024-03-22 18:10 ` dpdklab
2024-03-22 18:10 ` dpdklab
2024-03-22 18:11 ` dpdklab
2024-03-22 18:11 ` dpdklab
2024-03-22 18:12 ` dpdklab
2024-03-22 18:14 ` dpdklab
2024-03-22 18:14 ` dpdklab
2024-03-22 18:14 ` dpdklab
2024-03-22 18:14 ` dpdklab
2024-03-22 18:15 ` dpdklab
2024-03-22 18:15 ` dpdklab
2024-03-22 18:15 ` dpdklab
2024-03-22 18:15 ` dpdklab
2024-03-22 18:16 ` dpdklab
2024-03-22 18:16 ` dpdklab
2024-03-22 18:16 ` dpdklab
2024-03-22 18:17 ` dpdklab
2024-03-22 18:17 ` dpdklab
2024-03-22 18:18 ` dpdklab
2024-03-22 18:18 ` dpdklab
2024-03-22 18:19 ` dpdklab
2024-03-22 18:19 ` dpdklab
2024-03-22 18:19 ` dpdklab
2024-03-22 18:23 ` dpdklab
2024-03-22 18:25 ` dpdklab
2024-03-22 18:28 ` dpdklab
2024-03-22 18:28 ` dpdklab
2024-03-22 18:29 ` dpdklab
2024-03-22 18:29 ` dpdklab
2024-03-22 18:29 ` dpdklab
2024-03-22 18:30 ` dpdklab
2024-03-22 18:32 ` dpdklab
2024-03-22 18:33 ` dpdklab
2024-03-22 18:34 ` dpdklab
2024-03-22 18:34 ` dpdklab
2024-03-22 18:35 ` dpdklab
2024-03-22 18:42 ` dpdklab
2024-03-22 18:43 ` dpdklab
2024-03-22 18:44 ` dpdklab
2024-03-22 18:51 ` dpdklab
2024-03-22 18:51 ` dpdklab
2024-03-22 18:51 ` dpdklab
2024-03-22 18:52 ` dpdklab
2024-03-22 18:53 ` dpdklab
2024-03-22 18:53 ` dpdklab
2024-03-22 18:55 ` dpdklab
2024-03-22 18:55 ` dpdklab
2024-03-22 18:55 ` dpdklab
2024-03-22 18:55 ` dpdklab
2024-03-22 18:56 ` dpdklab
2024-03-22 18:56 ` dpdklab
2024-03-22 18:56 ` dpdklab
2024-03-22 18:56 ` dpdklab
2024-03-22 18:58 ` dpdklab
2024-03-22 18:59 ` dpdklab
2024-03-22 18:59 ` dpdklab
2024-03-22 19:09 ` dpdklab
2024-03-22 20:26 ` dpdklab
2024-03-22 21:28 ` dpdklab
2024-03-24 5:20 ` dpdklab
2024-03-24 5:50 ` 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=202403221331.42MDVS7V1787505@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).