From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw130104 [PATCH] dma/idxd: add reset in the init routine
Date: Fri, 11 Aug 2023 11:08:17 +0800 [thread overview]
Message-ID: <202308110308.37B38Hkr3050171@localhost.localdomain> (raw)
In-Reply-To: <20230811021054.3848656-1-frank.du@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/130104
_Compilation OK_
Submitter: Frank Du <frank.du@intel.com>
Date: Fri, 11 Aug 2023 10:10:54 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 70b6941e4e22d67bc10495d1638234a7e974f582
130104 --> 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 prev parent reply other threads:[~2023-08-11 3:22 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230811021054.3848656-1-frank.du@intel.com>
2023-08-11 2:11 ` checkpatch
2023-08-11 2:58 ` 0-day Robot
2023-08-11 3:08 ` qemudev [this message]
2023-08-11 3:12 ` qemudev
2023-08-11 11:01 dpdklab
2023-08-11 11:02 dpdklab
2023-08-11 11:04 dpdklab
2023-08-11 11:05 dpdklab
2023-08-11 11:20 dpdklab
2023-08-11 11:28 dpdklab
2023-08-11 11:42 dpdklab
2023-08-11 11:52 dpdklab
2023-08-11 11:53 dpdklab
2023-08-11 11:54 dpdklab
2023-08-11 11:55 dpdklab
2023-08-11 11:56 dpdklab
2023-08-11 11:58 dpdklab
2023-08-11 11:58 dpdklab
2023-08-11 12:00 dpdklab
2023-08-11 12:00 dpdklab
2023-08-11 12:01 dpdklab
2023-08-11 12:02 dpdklab
2023-08-11 12:03 dpdklab
2023-08-11 12:03 dpdklab
2023-08-11 12:03 dpdklab
2023-08-11 12:05 dpdklab
2023-08-11 12:11 dpdklab
2023-08-11 12:12 dpdklab
2023-08-11 12:12 dpdklab
2023-08-11 12:33 dpdklab
2023-08-11 12:35 dpdklab
2023-08-11 12:38 dpdklab
2023-08-11 12:40 dpdklab
2023-08-11 12:56 dpdklab
2023-08-11 13:07 dpdklab
2023-08-11 13:41 dpdklab
2023-08-11 13:42 dpdklab
2023-08-11 14:02 dpdklab
2023-08-11 14:03 dpdklab
2023-08-11 14:06 dpdklab
2023-08-11 14:07 dpdklab
2023-08-11 14:08 dpdklab
2023-08-11 14:09 dpdklab
2023-08-11 14:11 dpdklab
2023-08-11 14:13 dpdklab
2023-08-11 14:14 dpdklab
2023-08-11 14:20 dpdklab
2023-08-11 22:33 dpdklab
2023-08-11 22:33 dpdklab
2023-08-11 22:33 dpdklab
2023-08-11 23:36 dpdklab
2023-08-11 23:43 dpdklab
2023-08-11 23:44 dpdklab
2023-08-11 23:46 dpdklab
2023-08-12 0:39 dpdklab
2023-08-12 0:40 dpdklab
2023-08-12 1:12 dpdklab
2023-08-12 3:53 dpdklab
2023-08-12 3:57 dpdklab
2023-08-12 4:02 dpdklab
2023-08-12 4:13 dpdklab
2023-08-12 4:30 dpdklab
2023-08-12 4:31 dpdklab
2023-08-13 18:58 dpdklab
2023-08-13 19:42 dpdklab
2023-08-13 21:07 dpdklab
2023-08-13 21:08 dpdklab
2023-08-13 21:09 dpdklab
2023-08-13 21:11 dpdklab
2023-08-13 21:11 dpdklab
2023-08-13 21:15 dpdklab
2023-08-13 21:24 dpdklab
2023-08-13 21:26 dpdklab
2023-08-13 21:31 dpdklab
2023-08-13 21:34 dpdklab
2023-08-13 21:36 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=202308110308.37B38Hkr3050171@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).