From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124815 [PATCH v2] lib/bpf: Rename bpf function names to avoid potential conflict with libpcap
Date: Mon, 6 Mar 2023 23:22:06 +0800 [thread overview]
Message-ID: <202303061522.326FM66Q137945@localhost.localdomain> (raw)
In-Reply-To: <20230306153218.40320-1-mars14850@gmail.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124815
_Compilation OK_
Submitter: Martzki <mars14850@gmail.com>
Date: Mon, 6 Mar 2023 23:32:18 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 4ef69b2877a24ddb89afaf4bb6f4e73bb52a605b
124815 --> 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:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230306153218.40320-1-mars14850@gmail.com>
2023-03-06 15:22 ` qemudev [this message]
2023-03-06 15:26 ` qemudev
2023-03-06 15:32 ` |WARNING| " checkpatch
2023-03-06 17:19 ` |SUCCESS| " 0-day Robot
2023-03-06 16:48 |SUCCESS| pw124815 [PATCH] [v2] " dpdklab
2023-03-06 16:52 dpdklab
2023-03-06 16:57 dpdklab
2023-03-06 17:03 dpdklab
2023-03-06 17:06 dpdklab
2023-03-06 17:18 dpdklab
2023-03-06 17:23 dpdklab
2023-03-06 17:30 dpdklab
2023-03-06 17:40 dpdklab
2023-03-06 17:42 dpdklab
2023-03-06 17:44 dpdklab
2023-03-06 18:19 dpdklab
2023-03-06 18:43 dpdklab
2023-03-06 18:45 dpdklab
2023-03-06 18:46 dpdklab
2023-03-06 18:49 dpdklab
2023-03-06 18:54 dpdklab
2023-03-06 19:04 dpdklab
2023-03-06 19:06 dpdklab
2023-03-06 19:14 dpdklab
2023-03-06 19:19 dpdklab
2023-03-06 19:21 dpdklab
2023-03-06 19:22 dpdklab
2023-03-06 19:24 dpdklab
2023-03-06 19:55 dpdklab
2023-03-06 19:55 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=202303061522.326FM66Q137945@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).