From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124830 [PATCH v2] net/iavf: fix iavf query stats in intr thread
Date: Tue, 7 Mar 2023 11:17:28 +0800 [thread overview]
Message-ID: <202303070317.3273HSGk473943@localhost.localdomain> (raw)
In-Reply-To: <20230307025533.1950861-1-kaiwenx.deng@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124830
_Compilation OK_
Submitter: Kaiwen Deng <kaiwenx.deng@intel.com>
Date: Tue, 7 Mar 2023 10:55:32 +0800
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 34fe803c051fd614831069318364830c9a369bc5
124830 --> 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-03-07 3:31 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230307025533.1950861-1-kaiwenx.deng@intel.com>
2023-03-07 3:17 ` qemudev [this message]
2023-03-07 3:21 ` qemudev
2023-03-07 3:29 ` |WARNING| " checkpatch
2023-03-07 5:19 ` |SUCCESS| " 0-day Robot
2023-03-07 4:30 |SUCCESS| pw124830 [PATCH] [v2] " dpdklab
2023-03-07 4:32 dpdklab
2023-03-07 4:37 dpdklab
2023-03-07 4:40 dpdklab
2023-03-07 4:41 dpdklab
2023-03-07 4:43 dpdklab
2023-03-07 4:44 dpdklab
2023-03-07 4:47 dpdklab
2023-03-07 4:49 dpdklab
2023-03-07 4:51 dpdklab
2023-03-07 4:57 dpdklab
2023-03-07 5:08 dpdklab
2023-03-07 5:10 dpdklab
2023-03-07 5:14 dpdklab
2023-03-07 5:19 dpdklab
2023-03-07 5:19 dpdklab
2023-03-07 5:21 dpdklab
2023-03-07 5:21 dpdklab
2023-03-07 5:25 dpdklab
2023-03-07 5:26 dpdklab
2023-03-07 5:28 dpdklab
2023-03-07 5:32 dpdklab
2023-03-07 5:35 dpdklab
2023-03-07 6:29 dpdklab
2023-03-07 7:39 dpdklab
2023-03-07 8:00 dpdklab
2023-03-07 8:00 dpdklab
2023-03-07 8:04 dpdklab
2023-03-07 8:05 dpdklab
2023-03-07 8:09 dpdklab
2023-03-07 8:22 dpdklab
2023-03-07 8:24 dpdklab
2023-03-07 8:32 dpdklab
2023-03-07 8:37 dpdklab
2023-03-07 8:40 dpdklab
2023-03-07 8:41 dpdklab
2023-03-07 8:43 dpdklab
2023-03-07 8:48 dpdklab
2023-03-07 8:48 dpdklab
2023-03-07 8:58 dpdklab
2023-03-07 9:02 dpdklab
2023-03-07 9:02 dpdklab
2023-03-07 9:03 dpdklab
2023-03-07 9:04 dpdklab
2023-03-07 9:05 dpdklab
2023-03-07 9:06 dpdklab
2023-03-07 9:12 dpdklab
2023-03-07 9:14 dpdklab
2023-03-07 9:16 dpdklab
2023-03-07 9:16 dpdklab
2023-03-07 9:19 dpdklab
2023-03-07 9:20 dpdklab
2023-03-07 9:28 dpdklab
2023-03-07 9:29 dpdklab
2023-03-07 9:42 dpdklab
2023-03-07 10:07 dpdklab
2023-03-07 11:43 dpdklab
2023-03-07 12:31 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=202303070317.3273HSGk473943@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).