From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw133871 [PATCH] net/sfc: fix null dereference in syslog
Date: Sat, 4 Nov 2023 15:19:23 +0800 [thread overview]
Message-ID: <202311040719.3A47JNEU131188@localhost.localdomain> (raw)
In-Reply-To: <tencent_3688599DB9EF8F116B918398669E9ED3C107@qq.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/133871
_Compilation OK_
Submitter: Weiguo Li <liwg06@foxmail.com>
Date: Sat, 4 Nov 2023 15:37:15 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: b0b0e2ecd7d8185d8d497881214cb1e906196323
133871 --> 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-11-04 7:40 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_3688599DB9EF8F116B918398669E9ED3C107@qq.com>
2023-11-04 7:19 ` qemudev [this message]
2023-11-04 7:23 ` qemudev
2023-11-04 7:38 ` |WARNING| " checkpatch
2023-11-04 9:06 ` |SUCCESS| " 0-day Robot
2023-11-04 18:07 dpdklab
2023-11-04 18:08 dpdklab
2023-11-04 18:09 dpdklab
2023-11-04 18:10 dpdklab
2023-11-04 18:11 dpdklab
2023-11-04 18:11 dpdklab
2023-11-04 18:11 dpdklab
2023-11-04 18:12 dpdklab
2023-11-04 18:12 dpdklab
2023-11-04 18:13 dpdklab
2023-11-04 18:13 dpdklab
2023-11-04 18:13 dpdklab
2023-11-04 18:14 dpdklab
2023-11-04 18:14 dpdklab
2023-11-04 18:14 dpdklab
2023-11-04 18:14 dpdklab
2023-11-04 18:14 dpdklab
2023-11-04 18:14 dpdklab
2023-11-04 18:15 dpdklab
2023-11-04 18:15 dpdklab
2023-11-04 18:16 dpdklab
2023-11-04 18:16 dpdklab
2023-11-04 18:17 dpdklab
2023-11-04 18:17 dpdklab
2023-11-04 18:17 dpdklab
2023-11-04 18:17 dpdklab
2023-11-04 18:18 dpdklab
2023-11-04 18:18 dpdklab
2023-11-04 18:18 dpdklab
2023-11-04 18:19 dpdklab
2023-11-04 18:19 dpdklab
2023-11-04 18:19 dpdklab
2023-11-04 18:19 dpdklab
2023-11-04 18:20 dpdklab
2023-11-04 18:20 dpdklab
2023-11-04 18:20 dpdklab
2023-11-04 18:21 dpdklab
2023-11-04 18:21 dpdklab
2023-11-04 18:21 dpdklab
2023-11-04 18:21 dpdklab
2023-11-04 18:21 dpdklab
2023-11-04 18:21 dpdklab
2023-11-04 18:22 dpdklab
2023-11-04 18:22 dpdklab
2023-11-04 18:23 dpdklab
2023-11-04 18:23 dpdklab
2023-11-04 18:24 dpdklab
2023-11-04 18:24 dpdklab
2023-11-04 18:24 dpdklab
2023-11-04 18:25 dpdklab
2023-11-04 18:25 dpdklab
2023-11-04 18:26 dpdklab
2023-11-04 18:28 dpdklab
2023-11-04 18:36 dpdklab
2023-11-04 18:37 dpdklab
2023-11-04 19:35 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=202311040719.3A47JNEU131188@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).