From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw143676 [PATCH] net/pcap: use pcap_next_ex to track errors
Date: Thu, 5 Sep 2024 23:44:55 +0800 [thread overview]
Message-ID: <202409051544.485Fitmt2191928@localhost.localdomain> (raw)
In-Reply-To: <20240905161129.73553-1-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/143676
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thu, 5 Sep 2024 09:10:40 -0700
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 523fd7b3adfdf5a87651e8ca33bc69223b3211d5
143676 --> 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-09-05 16:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240905161129.73553-1-stephen@networkplumber.org>
2024-09-05 15:44 ` qemudev [this message]
2024-09-05 15:49 ` qemudev
2024-09-05 16:11 ` checkpatch
2024-09-05 17:05 ` 0-day Robot
2024-09-06 4:39 ` |SUCCESS| pw143676 [PATCH] net/pcap: use pcap_next_ex to track error dpdklab
2024-09-06 6:20 ` dpdklab
2024-09-06 6:42 ` |PENDING| " dpdklab
2024-09-06 6:43 ` dpdklab
2024-09-06 6:55 ` |SUCCESS| " dpdklab
2024-09-06 8:39 ` dpdklab
2024-09-06 8:40 ` dpdklab
2024-09-06 8:41 ` dpdklab
2024-09-06 9:01 ` dpdklab
2024-09-06 11:00 ` dpdklab
2024-09-06 11:18 ` dpdklab
2024-09-06 11:19 ` dpdklab
2024-09-06 11:20 ` dpdklab
2024-09-06 11:21 ` dpdklab
2024-09-06 14:34 ` dpdklab
2024-09-06 15:03 ` dpdklab
2024-09-07 19:25 ` dpdklab
2024-09-17 16:23 ` dpdklab
2024-09-17 16:44 ` 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=202409051544.485Fitmt2191928@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).