From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw129672 [PATCH v2 ] tap: fix build of TAP BPF program
Date: Fri, 21 Jul 2023 01:33:15 +0800 [thread overview]
Message-ID: <202307201733.36KHXF441306210@localhost.localdomain> (raw)
In-Reply-To: <20230720174558.10265-1-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/129672
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thu, 20 Jul 2023 10:45:58 -0700
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: fbafb3676c482dab60c0b5465b47f2ea33893a36
129672 --> 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-07-20 17:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230720174558.10265-1-stephen@networkplumber.org>
2023-07-20 17:33 ` qemudev [this message]
2023-07-20 17:37 ` qemudev
2023-07-20 17:47 ` |WARNING| " checkpatch
2023-07-20 18:38 ` |SUCCESS| " 0-day Robot
2023-07-20 18:37 |SUCCESS| pw129672 [PATCH] [v2] " dpdklab
2023-07-20 18:40 dpdklab
2023-07-20 18:40 dpdklab
2023-07-20 18:42 dpdklab
2023-07-20 18:42 dpdklab
2023-07-20 18:42 dpdklab
2023-07-20 18:45 dpdklab
2023-07-20 18:46 dpdklab
2023-07-20 18:48 dpdklab
2023-07-20 18:50 dpdklab
2023-07-20 18:50 dpdklab
2023-07-20 18:51 dpdklab
2023-07-20 18:52 dpdklab
2023-07-20 19:00 dpdklab
2023-07-20 19:07 dpdklab
2023-07-20 19:07 dpdklab
2023-07-20 19:17 dpdklab
2023-07-20 19:18 dpdklab
2023-07-20 19:37 dpdklab
2023-07-20 19:53 dpdklab
2023-07-20 20:18 dpdklab
2023-07-20 21:43 dpdklab
2023-07-20 23:18 dpdklab
2023-07-20 23:59 dpdklab
2023-07-21 0:24 dpdklab
2023-07-21 0:30 dpdklab
2023-07-21 0:34 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=202307201733.36KHXF441306210@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).