From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124816 [PATCH v3] lib/bpf: Rename bpf function names to avoid potential conflict with libpcap
Date: Mon, 6 Mar 2023 23:31:20 +0800 [thread overview]
Message-ID: <202303061531.326FVKiP189147@localhost.localdomain> (raw)
In-Reply-To: <20230306154216.41154-1-mars14850@gmail.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124816
_Compilation OK_
Submitter: Martzki <mars14850@gmail.com>
Date: Mon, 6 Mar 2023 23:42:15 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 4ef69b2877a24ddb89afaf4bb6f4e73bb52a605b
124816 --> 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:[~2023-03-06 15:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230306154216.41154-1-mars14850@gmail.com>
2023-03-06 15:31 ` qemudev [this message]
2023-03-06 15:35 ` qemudev
2023-03-06 15:42 ` |WARNING| " checkpatch
2023-03-06 17:39 ` |SUCCESS| " 0-day Robot
2023-03-06 21:05 |SUCCESS| pw124816 [PATCH] [v3] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-03-06 21:04 dpdklab
2023-03-06 20:42 dpdklab
2023-03-06 20:31 dpdklab
2023-03-06 20:30 dpdklab
2023-03-06 20:30 dpdklab
2023-03-06 20:25 dpdklab
2023-03-06 20:14 dpdklab
2023-03-06 20:03 dpdklab
2023-03-06 20:02 dpdklab
2023-03-06 20:01 dpdklab
2023-03-06 19:59 dpdklab
2023-03-06 19:57 dpdklab
2023-03-06 19:55 dpdklab
2023-03-06 19:51 dpdklab
2023-03-06 19:48 dpdklab
2023-03-06 19:27 dpdklab
2023-03-06 18:58 dpdklab
2023-03-06 17:47 dpdklab
2023-03-06 17:45 dpdklab
2023-03-06 17:35 dpdklab
2023-03-06 17:31 dpdklab
2023-03-06 17:27 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=202303061531.326FVKiP189147@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).