From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140026 [PATCH] bpf: don't verify classic bpfs
Date: Sun, 12 May 2024 13:31:11 +0800 [thread overview]
Message-ID: <202405120531.44C5VBvH1592892@localhost.localdomain> (raw)
In-Reply-To: <20240512055545.98297-1-yoav.w@claroty.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140026
_Compilation OK_
Submitter: Yoav Winstein <yoav.w@claroty.com>
Date: Sun, 12 May 2024 08:55:45 +0300
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
140026 --> 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-05-12 5:59 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240512055545.98297-1-yoav.w@claroty.com>
2024-05-12 5:31 ` qemudev [this message]
2024-05-12 5:36 ` qemudev
2024-05-12 5:56 ` |WARNING| " checkpatch
2024-05-12 6:44 ` |FAILURE| " 0-day Robot
2024-05-13 11:50 ` |SUCCESS| " dpdklab
2024-05-13 11:52 ` dpdklab
2024-05-13 11:53 ` dpdklab
2024-05-13 11:54 ` dpdklab
2024-05-13 11:54 ` dpdklab
2024-05-13 12:00 ` dpdklab
2024-05-13 12:01 ` |WARNING| " dpdklab
2024-05-13 12:02 ` dpdklab
2024-05-13 12:02 ` |SUCCESS| " dpdklab
2024-05-13 12:02 ` |WARNING| " dpdklab
2024-05-13 12:25 ` dpdklab
2024-05-13 12:27 ` dpdklab
2024-05-13 12:27 ` |SUCCESS| " dpdklab
2024-05-13 12:28 ` dpdklab
2024-05-13 12:28 ` dpdklab
2024-05-13 12:29 ` dpdklab
2024-05-13 12:29 ` dpdklab
2024-05-13 12:30 ` dpdklab
2024-05-13 12:30 ` |WARNING| " dpdklab
2024-05-13 12:30 ` |SUCCESS| " dpdklab
2024-05-13 12:30 ` dpdklab
2024-05-13 12:31 ` dpdklab
2024-05-13 12:31 ` dpdklab
2024-05-13 12:32 ` dpdklab
2024-05-13 12:32 ` dpdklab
2024-05-13 12:32 ` dpdklab
2024-05-13 12:33 ` dpdklab
2024-05-13 12:33 ` dpdklab
2024-05-13 12:33 ` |WARNING| " dpdklab
2024-05-13 12:33 ` dpdklab
2024-05-13 12:36 ` dpdklab
2024-05-13 12:36 ` |SUCCESS| " dpdklab
2024-05-13 12:38 ` dpdklab
2024-05-13 12:44 ` dpdklab
2024-05-13 12:45 ` dpdklab
2024-05-13 12:45 ` dpdklab
2024-05-13 12:46 ` dpdklab
2024-05-13 12:46 ` |WARNING| " dpdklab
2024-05-13 12:47 ` |SUCCESS| " dpdklab
2024-05-13 12:47 ` |WARNING| " dpdklab
2024-05-13 12:47 ` |SUCCESS| " dpdklab
2024-05-13 12:47 ` dpdklab
2024-05-13 12:47 ` dpdklab
2024-05-13 12:47 ` dpdklab
2024-05-13 12:47 ` dpdklab
2024-05-13 12:48 ` dpdklab
2024-05-13 12:48 ` dpdklab
2024-05-13 12:48 ` |WARNING| " dpdklab
2024-05-13 12:48 ` |SUCCESS| " dpdklab
2024-05-13 12:48 ` dpdklab
2024-05-13 12:49 ` dpdklab
2024-05-13 12:50 ` dpdklab
2024-05-13 12:58 ` dpdklab
2024-05-13 12:59 ` dpdklab
2024-05-13 13:00 ` dpdklab
2024-05-13 13:00 ` dpdklab
2024-05-13 13:01 ` dpdklab
2024-05-13 13:02 ` dpdklab
2024-05-13 13:03 ` dpdklab
2024-05-13 13:04 ` dpdklab
2024-05-13 13:05 ` dpdklab
2024-05-13 13:06 ` dpdklab
2024-05-13 13:07 ` dpdklab
2024-05-13 13:12 ` dpdklab
2024-05-13 13:13 ` dpdklab
2024-05-13 13:14 ` dpdklab
2024-05-13 13:14 ` dpdklab
2024-05-13 13:18 ` dpdklab
2024-05-13 13:18 ` dpdklab
2024-05-13 13:20 ` dpdklab
2024-05-13 13:21 ` dpdklab
2024-05-13 13:22 ` dpdklab
2024-05-13 13:22 ` dpdklab
2024-05-13 13:22 ` dpdklab
2024-05-13 13:22 ` dpdklab
2024-05-13 13:22 ` dpdklab
2024-05-13 13:23 ` dpdklab
2024-05-13 13:23 ` dpdklab
2024-05-13 13:24 ` dpdklab
2024-05-13 13:25 ` dpdklab
2024-05-13 13:25 ` dpdklab
2024-05-13 13:32 ` dpdklab
2024-05-13 13:33 ` dpdklab
2024-05-13 13:37 ` dpdklab
2024-05-13 13:37 ` dpdklab
2024-05-13 13:40 ` dpdklab
2024-05-13 13:44 ` dpdklab
2024-05-13 13:48 ` dpdklab
2024-05-13 14:09 ` 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=202405120531.44C5VBvH1592892@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).