From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw143120 [PATCH] net/tap: avoid memcpy with NULL arg
Date: Wed, 14 Aug 2024 10:22:04 +0800 [thread overview]
Message-ID: <202408140222.47E2M4qV1715071@localhost.localdomain> (raw)
In-Reply-To: <20240814023426.124491-1-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/143120
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tue, 13 Aug 2024 19:34:16 -0700
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: e0f7ebe88ab4588dd352e9ec14270ce4e3b1470b
143120 --> 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-08-14 2:51 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240814023426.124491-1-stephen@networkplumber.org>
2024-08-14 2:22 ` qemudev [this message]
2024-08-14 2:26 ` qemudev
2024-08-14 2:35 ` checkpatch
2024-08-14 3:22 ` 0-day Robot
2024-08-14 3:49 ` dpdklab
2024-08-14 3:51 ` dpdklab
2024-08-14 3:54 ` dpdklab
2024-08-14 3:54 ` |PENDING| " dpdklab
2024-08-14 3:57 ` |SUCCESS| " dpdklab
2024-08-14 3:57 ` dpdklab
2024-08-14 3:59 ` |PENDING| " dpdklab
2024-08-14 3:59 ` dpdklab
2024-08-14 4:00 ` dpdklab
2024-08-14 4:03 ` dpdklab
2024-08-14 4:05 ` dpdklab
2024-08-14 4:05 ` dpdklab
2024-08-14 4:06 ` dpdklab
2024-08-14 4:06 ` dpdklab
2024-08-14 4:06 ` dpdklab
2024-08-14 4:07 ` dpdklab
2024-08-14 4:08 ` |SUCCESS| " dpdklab
2024-08-14 4:08 ` |PENDING| " dpdklab
2024-08-14 4:11 ` dpdklab
2024-08-14 4:11 ` |SUCCESS| " dpdklab
2024-08-14 4:12 ` |PENDING| " dpdklab
2024-08-14 4:12 ` dpdklab
2024-08-14 4:12 ` dpdklab
2024-08-14 4:13 ` dpdklab
2024-08-14 4:14 ` |SUCCESS| " dpdklab
2024-08-14 4:14 ` |PENDING| " dpdklab
2024-08-14 4:14 ` dpdklab
2024-08-14 4:14 ` dpdklab
2024-08-14 4:15 ` dpdklab
2024-08-14 4:15 ` dpdklab
2024-08-14 4:15 ` |SUCCESS| " dpdklab
2024-08-14 4:15 ` |PENDING| " dpdklab
2024-08-14 4:16 ` dpdklab
2024-08-14 4:16 ` dpdklab
2024-08-14 4:16 ` dpdklab
2024-08-14 4:17 ` dpdklab
2024-08-14 4:17 ` dpdklab
2024-08-14 4:17 ` dpdklab
2024-08-14 4:18 ` dpdklab
2024-08-14 4:18 ` dpdklab
2024-08-14 4:18 ` dpdklab
2024-08-14 4:18 ` |SUCCESS| " dpdklab
2024-08-14 4:19 ` |PENDING| " dpdklab
2024-08-14 4:21 ` dpdklab
2024-08-14 4:21 ` dpdklab
2024-08-14 4:21 ` dpdklab
2024-08-14 4:21 ` dpdklab
2024-08-14 4:22 ` dpdklab
2024-08-14 4:22 ` dpdklab
2024-08-14 4:22 ` dpdklab
2024-08-14 4:23 ` dpdklab
2024-08-14 4:23 ` dpdklab
2024-08-14 4:25 ` dpdklab
2024-08-14 4:25 ` dpdklab
2024-08-14 4:25 ` dpdklab
2024-08-14 4:26 ` dpdklab
2024-08-14 4:26 ` dpdklab
2024-08-14 4:27 ` dpdklab
2024-08-14 4:27 ` dpdklab
2024-08-14 4:27 ` dpdklab
2024-08-14 4:28 ` dpdklab
2024-08-14 4:28 ` dpdklab
2024-08-14 4:28 ` dpdklab
2024-08-14 4:29 ` |SUCCESS| " dpdklab
2024-08-14 4:29 ` |PENDING| " dpdklab
2024-08-14 4:29 ` dpdklab
2024-08-14 4:29 ` dpdklab
2024-08-14 4:30 ` dpdklab
2024-08-14 4:30 ` dpdklab
2024-08-14 4:32 ` dpdklab
2024-08-14 4:33 ` dpdklab
2024-08-14 4:35 ` dpdklab
2024-08-14 4:35 ` dpdklab
2024-08-14 4:35 ` |SUCCESS| " dpdklab
2024-08-14 4:37 ` |PENDING| " dpdklab
2024-08-14 4:38 ` dpdklab
2024-08-14 4:40 ` |SUCCESS| " dpdklab
2024-08-14 4:40 ` dpdklab
2024-08-14 4:42 ` |PENDING| " dpdklab
2024-08-14 4:44 ` dpdklab
2024-08-14 4:48 ` dpdklab
2024-08-14 4:49 ` |SUCCESS| " dpdklab
2024-08-14 4:50 ` |PENDING| " dpdklab
2024-08-14 4:51 ` |SUCCESS| " dpdklab
2024-08-14 4:52 ` dpdklab
2024-08-14 4:59 ` dpdklab
2024-08-14 5:04 ` dpdklab
2024-08-14 5:09 ` dpdklab
2024-08-14 5:32 ` |PENDING| " dpdklab
2024-08-14 5:53 ` dpdklab
2024-08-14 5:57 ` |SUCCESS| " 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=202408140222.47E2M4qV1715071@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).