From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw131374 [PATCH] bus/pci: fix device ID print
Date: Wed, 13 Sep 2023 18:31:56 +0800 [thread overview]
Message-ID: <202309131031.38DAVuC42015639@localhost.localdomain> (raw)
In-Reply-To: <20230913082333.1056156-1-qiming.yang@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/131374
_Compilation OK_
Submitter: Qiming Yang <qiming.yang@intel.com>
Date: Wed, 13 Sep 2023 08:23:33 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: e92ba1426914db1d224dd5e9a1743657681b8814
131374 --> 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-09-13 10:52 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230913082333.1056156-1-qiming.yang@intel.com>
2023-09-13 8:45 ` checkpatch
2023-09-13 9:39 ` 0-day Robot
2023-09-13 10:31 ` qemudev [this message]
2023-09-13 10:35 ` qemudev
2023-09-13 15:13 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-09-13 14:44 dpdklab
2023-09-13 14:22 dpdklab
2023-09-13 14:21 dpdklab
2023-09-13 14:21 dpdklab
2023-09-13 14:20 dpdklab
2023-09-13 14:18 dpdklab
2023-09-13 14:14 dpdklab
2023-09-13 14:14 dpdklab
2023-09-13 14:14 dpdklab
2023-09-13 14:14 dpdklab
2023-09-13 14:13 dpdklab
2023-09-13 14:12 dpdklab
2023-09-13 14:12 dpdklab
2023-09-13 14:11 dpdklab
2023-09-13 14:11 dpdklab
2023-09-13 14:07 dpdklab
2023-09-13 13:56 dpdklab
2023-09-13 13:56 dpdklab
2023-09-13 13:56 dpdklab
2023-09-13 13:56 dpdklab
2023-09-13 13:56 dpdklab
2023-09-13 13:56 dpdklab
2023-09-13 13:56 dpdklab
2023-09-13 13:55 dpdklab
2023-09-13 13:55 dpdklab
2023-09-13 13:55 dpdklab
2023-09-13 13:55 dpdklab
2023-09-13 13:55 dpdklab
2023-09-13 13:55 dpdklab
2023-09-13 13:55 dpdklab
2023-09-13 13:55 dpdklab
2023-09-13 13:55 dpdklab
2023-09-13 13:54 dpdklab
2023-09-13 13:54 dpdklab
2023-09-13 13:54 dpdklab
2023-09-13 13:54 dpdklab
2023-09-13 13:54 dpdklab
2023-09-13 13:54 dpdklab
2023-09-13 13:53 dpdklab
2023-09-13 13:53 dpdklab
2023-09-13 13:51 dpdklab
2023-09-13 13:42 dpdklab
2023-09-13 9:45 dpdklab
2023-09-13 9:42 dpdklab
2023-09-13 9:42 dpdklab
2023-09-13 9:38 dpdklab
2023-09-13 9:36 dpdklab
2023-09-13 9:34 dpdklab
2023-09-13 9:32 dpdklab
2023-09-13 9:32 dpdklab
2023-09-13 9:32 dpdklab
2023-09-13 9:31 dpdklab
2023-09-13 9:29 dpdklab
2023-09-13 9:27 dpdklab
2023-09-13 9:27 dpdklab
2023-09-13 9:26 dpdklab
2023-09-13 9:26 dpdklab
2023-09-13 9:23 dpdklab
2023-09-13 9:22 dpdklab
2023-09-13 9:21 dpdklab
2023-09-13 9:21 dpdklab
2023-09-13 9:19 dpdklab
2023-09-13 9:19 dpdklab
2023-09-13 9:19 dpdklab
2023-09-13 9:18 dpdklab
2023-09-13 9:18 dpdklab
2023-09-13 9:18 dpdklab
2023-09-13 9:18 dpdklab
2023-09-13 9:18 dpdklab
2023-09-13 9:18 dpdklab
2023-09-13 9:18 dpdklab
2023-09-13 9:18 dpdklab
2023-09-13 9:17 dpdklab
2023-09-13 9:17 dpdklab
2023-09-13 9:17 dpdklab
2023-09-13 9:17 dpdklab
2023-09-13 9:17 dpdklab
2023-09-13 9:17 dpdklab
2023-09-13 9:16 dpdklab
2023-09-13 9:16 dpdklab
2023-09-13 9:16 dpdklab
2023-09-13 9:14 dpdklab
2023-09-13 9:14 dpdklab
2023-09-13 9:14 dpdklab
2023-09-13 9:13 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=202309131031.38DAVuC42015639@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).