From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124572 [PATCH] dma/idxd: add verbose option to config script
Date: Wed, 1 Mar 2023 16:15:58 +0800 [thread overview]
Message-ID: <202303010815.3218Fwh1952529@localhost.localdomain> (raw)
In-Reply-To: <20230228145035.11828-1-bruce.richardson@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124572
_Compilation OK_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Tue, 28 Feb 2023 14:50:36 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7710b5d15a014872a3aaf646668dafa928ca8473
124572 --> 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-03-01 8:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230228145035.11828-1-bruce.richardson@intel.com>
2023-02-28 14:53 ` checkpatch
2023-02-28 16:39 ` 0-day Robot
2023-03-01 8:15 ` qemudev [this message]
2023-03-01 8:16 ` qemudev
2023-02-28 16:37 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-02-28 16:37 dpdklab
2023-02-28 16:35 dpdklab
2023-02-28 16:34 dpdklab
2023-02-28 16:24 dpdklab
2023-02-28 16:21 dpdklab
2023-02-28 16:17 dpdklab
2023-02-28 16:12 dpdklab
2023-02-28 16:10 dpdklab
2023-02-28 16:07 dpdklab
2023-02-28 16:07 dpdklab
2023-02-28 16:05 dpdklab
2023-02-28 16:04 dpdklab
2023-02-28 15:59 dpdklab
2023-02-28 15:56 dpdklab
2023-02-28 15:52 dpdklab
2023-02-28 15:50 dpdklab
2023-02-28 15:44 dpdklab
2023-02-28 15:39 dpdklab
2023-02-28 15:36 dpdklab
2023-02-28 15:32 dpdklab
2023-02-28 15:32 dpdklab
2023-02-28 15:32 dpdklab
2023-02-28 15:28 dpdklab
2023-02-28 15:27 dpdklab
2023-02-28 15:24 dpdklab
2023-02-28 15:19 dpdklab
2023-02-28 15:17 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=202303010815.3218Fwh1952529@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).