From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124797 [PATCH] lib/bpf: Rename 'bpf_validate' to avoid potential conflict with libpcap
Date: Mon, 6 Mar 2023 15:05:12 +0800 [thread overview]
Message-ID: <202303060705.32675CI13956529@localhost.localdomain> (raw)
In-Reply-To: <20230303135655.78749-1-mars14850@gmail.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124797
_Compilation OK_
Submitter: Martzki <mars14850@gmail.com>
Date: Fri, 3 Mar 2023 21:56:54 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 4ef69b2877a24ddb89afaf4bb6f4e73bb52a605b
124797 --> 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-06 7:19 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230303135655.78749-1-mars14850@gmail.com>
2023-03-03 13:58 ` |WARNING| " checkpatch
2023-03-03 15:59 ` |SUCCESS| " 0-day Robot
2023-03-06 7:05 ` qemudev [this message]
2023-03-06 7:05 ` qemudev
2023-03-05 7:39 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-03-05 7:39 dpdklab
2023-03-05 7:38 dpdklab
2023-03-05 7:31 dpdklab
2023-03-05 7:21 dpdklab
2023-03-05 7:19 dpdklab
2023-03-05 7:16 dpdklab
2023-03-05 7:15 dpdklab
2023-03-05 7:12 dpdklab
2023-03-05 7:07 dpdklab
2023-03-05 7:06 dpdklab
2023-03-05 7:05 dpdklab
2023-03-05 7:02 dpdklab
2023-03-05 6:57 dpdklab
2023-03-05 6:56 dpdklab
2023-03-05 6:54 dpdklab
2023-03-05 6:52 dpdklab
2023-03-05 6:45 dpdklab
2023-03-05 6:44 dpdklab
2023-03-05 6:43 dpdklab
2023-03-05 6:36 dpdklab
2023-03-05 6:31 dpdklab
2023-03-05 6:26 dpdklab
2023-03-05 6:21 dpdklab
2023-03-05 6:16 dpdklab
2023-03-05 6:10 dpdklab
2023-03-05 6:08 dpdklab
2023-03-04 8:43 dpdklab
2023-03-04 8:05 dpdklab
2023-03-04 7:38 dpdklab
2023-03-04 7:31 dpdklab
2023-03-04 1:34 dpdklab
2023-03-04 1:24 dpdklab
2023-03-03 18:44 dpdklab
2023-03-03 18:07 dpdklab
2023-03-03 17:48 dpdklab
2023-03-03 17:43 dpdklab
2023-03-03 17:39 dpdklab
2023-03-03 17:36 dpdklab
2023-03-03 17:35 dpdklab
2023-03-03 17:34 dpdklab
2023-03-03 17:31 dpdklab
2023-03-03 17:30 dpdklab
2023-03-03 17:29 dpdklab
2023-03-03 17:28 dpdklab
2023-03-03 17:27 dpdklab
2023-03-03 17:26 dpdklab
2023-03-03 17:01 dpdklab
2023-03-03 16:57 dpdklab
2023-03-03 16:49 dpdklab
2023-03-03 16:48 dpdklab
2023-03-03 16:47 dpdklab
2023-03-03 16:46 dpdklab
2023-03-03 16:44 dpdklab
2023-03-03 16:43 dpdklab
2023-03-03 16:43 dpdklab
2023-03-03 16:40 dpdklab
2023-03-03 16:37 dpdklab
2023-03-03 16:30 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=202303060705.32675CI13956529@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).