From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw135693 [PATCH v3] net/iavf: fix VF startup coredump
Date: Wed, 3 Jan 2024 11:00:44 +0800 [thread overview]
Message-ID: <202401030300.40330i44260482@localhost.localdomain> (raw)
In-Reply-To: <20240103104207.125714-1-shiyangx.he@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/135693
_Compilation OK_
Submitter: Shiyang He <shiyangx.he@intel.com>
Date: Wed, 3 Jan 2024 10:42:07 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: bbb278d68ccd189f410d64d71831e26f9f341d73
135693 --> 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-03 3:21 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240103104207.125714-1-shiyangx.he@intel.com>
2024-01-03 3:00 ` qemudev [this message]
2024-01-03 3:05 ` qemudev
2024-01-03 3:20 ` checkpatch
2024-01-03 4:11 ` 0-day Robot
2024-01-03 4:55 |SUCCESS| pw135693 [PATCH] [v3] " dpdklab
2024-01-03 4:58 dpdklab
2024-01-03 5:01 dpdklab
2024-01-03 5:11 dpdklab
2024-01-03 5:17 dpdklab
2024-01-03 5:32 dpdklab
2024-01-03 5:32 dpdklab
2024-01-03 5:44 dpdklab
2024-01-03 5:47 dpdklab
2024-01-03 5:52 dpdklab
2024-01-03 5:53 dpdklab
2024-01-03 5:55 dpdklab
2024-01-03 5:55 dpdklab
2024-01-03 5:59 dpdklab
2024-01-03 6:01 dpdklab
2024-01-03 6:07 dpdklab
2024-01-03 6:07 dpdklab
2024-01-03 6:09 dpdklab
2024-01-03 6:09 dpdklab
2024-01-03 6:11 dpdklab
2024-01-03 6:12 dpdklab
2024-01-03 6:12 dpdklab
2024-01-03 6:13 dpdklab
2024-01-03 6:14 dpdklab
2024-01-03 6:15 dpdklab
2024-01-03 6:16 dpdklab
2024-01-03 6:16 dpdklab
2024-01-03 6:18 dpdklab
2024-01-03 6:18 dpdklab
2024-01-03 6:18 dpdklab
2024-01-03 6:19 dpdklab
2024-01-03 6:19 dpdklab
2024-01-03 6:25 dpdklab
2024-01-03 6:27 dpdklab
2024-01-03 6:27 dpdklab
2024-01-03 6:27 dpdklab
2024-01-03 6:27 dpdklab
2024-01-03 6:27 dpdklab
2024-01-03 6:28 dpdklab
2024-01-03 6:28 dpdklab
2024-01-03 6:28 dpdklab
2024-01-03 6:29 dpdklab
2024-01-03 6:29 dpdklab
2024-01-03 6:29 dpdklab
2024-01-03 6:29 dpdklab
2024-01-03 6:30 dpdklab
2024-01-03 6:30 dpdklab
2024-01-03 6:32 dpdklab
2024-01-03 6:32 dpdklab
2024-01-03 6:32 dpdklab
2024-01-03 6:32 dpdklab
2024-01-03 6:33 dpdklab
2024-01-03 6:33 dpdklab
2024-01-03 6:33 dpdklab
2024-01-03 6:33 dpdklab
2024-01-03 6:33 dpdklab
2024-01-03 6:39 dpdklab
2024-01-03 6:39 dpdklab
2024-01-03 6:39 dpdklab
2024-01-03 6:45 dpdklab
2024-01-03 6:54 dpdklab
2024-01-03 7:08 dpdklab
2024-01-03 7:11 dpdklab
2024-01-03 7:28 dpdklab
2024-01-03 8:31 dpdklab
2024-01-03 8:47 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=202401030300.40330i44260482@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).