From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw136091 [PATCH] net/iavf: fix access to null value
Date: Wed, 24 Jan 2024 10:08:22 +0800 [thread overview]
Message-ID: <202401240208.40O28Mv92014403@localhost.localdomain> (raw)
In-Reply-To: <20240124020555.3336924-1-mingjinx.ye@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/136091
_Compilation OK_
Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Wed, 24 Jan 2024 02:05:55 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 4e7732d6c4c64514dc26c3cc0203d19851b5f5aa
136091 --> 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-01-24 2:33 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240124020555.3336924-1-mingjinx.ye@intel.com>
2024-01-24 2:08 ` qemudev [this message]
2024-01-24 2:12 ` qemudev
2024-01-24 2:26 ` checkpatch
2024-01-24 6:41 ` 0-day Robot
2024-01-24 6:11 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2024-01-24 5:57 dpdklab
2024-01-24 4:37 dpdklab
2024-01-24 4:15 dpdklab
2024-01-24 4:13 dpdklab
2024-01-24 4:10 dpdklab
2024-01-24 4:08 dpdklab
2024-01-24 4:08 dpdklab
2024-01-24 4:07 dpdklab
2024-01-24 4:07 dpdklab
2024-01-24 4:07 dpdklab
2024-01-24 4:06 dpdklab
2024-01-24 4:06 dpdklab
2024-01-24 4:05 dpdklab
2024-01-24 4:04 dpdklab
2024-01-24 3:50 dpdklab
2024-01-24 3:47 dpdklab
2024-01-24 3:46 dpdklab
2024-01-24 3:46 dpdklab
2024-01-24 3:45 dpdklab
2024-01-24 3:44 dpdklab
2024-01-24 3:43 dpdklab
2024-01-24 3:43 dpdklab
2024-01-24 3:40 dpdklab
2024-01-24 3:40 dpdklab
2024-01-24 3:39 dpdklab
2024-01-24 3:39 dpdklab
2024-01-24 3:38 dpdklab
2024-01-24 3:38 dpdklab
2024-01-24 3:38 dpdklab
2024-01-24 3:37 dpdklab
2024-01-24 3:37 dpdklab
2024-01-24 3:37 dpdklab
2024-01-24 3:36 dpdklab
2024-01-24 3:36 dpdklab
2024-01-24 3:36 dpdklab
2024-01-24 3:35 dpdklab
2024-01-24 3:35 dpdklab
2024-01-24 3:35 dpdklab
2024-01-24 3:34 dpdklab
2024-01-24 3:34 dpdklab
2024-01-24 3:33 dpdklab
2024-01-24 3:33 dpdklab
2024-01-24 3:32 dpdklab
2024-01-24 3:32 dpdklab
2024-01-24 3:32 dpdklab
2024-01-24 3:31 dpdklab
2024-01-24 3:29 dpdklab
2024-01-24 3:29 dpdklab
2024-01-24 3:28 dpdklab
2024-01-24 3:28 dpdklab
2024-01-24 3:27 dpdklab
2024-01-24 3:27 dpdklab
2024-01-24 3:26 dpdklab
2024-01-24 3:26 dpdklab
2024-01-24 3:25 dpdklab
2024-01-24 3:25 dpdklab
2024-01-24 3:24 dpdklab
2024-01-24 3:24 dpdklab
2024-01-24 3:23 dpdklab
2024-01-24 3:23 dpdklab
2024-01-24 3:22 dpdklab
2024-01-24 3:21 dpdklab
2024-01-24 3:21 dpdklab
2024-01-24 3:20 dpdklab
2024-01-24 3:13 dpdklab
2024-01-24 3:12 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=202401240208.40O28Mv92014403@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).