From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw143425 [PATCH v2] bus/pci: don't open uio device in secondary process
Date: Thu, 29 Aug 2024 16:31:16 +0800 [thread overview]
Message-ID: <202408290831.47T8VG4K2672070@localhost.localdomain> (raw)
In-Reply-To: <20240829085724.270041-1-konrad.sztyber@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/143425
_Compilation OK_
Submitter: Konrad Sztyber <konrad.sztyber@intel.com>
Date: Thu, 29 Aug 2024 10:57:24 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: cb9187bc5c2b4bab0ad80194ac3b60491de14e8c
143425 --> 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-08-29 9:00 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240829085724.270041-1-konrad.sztyber@intel.com>
2024-08-29 8:31 ` qemudev [this message]
2024-08-29 8:35 ` qemudev
2024-08-29 8:59 ` |WARNING| " checkpatch
2024-08-29 10:03 ` |SUCCESS| " 0-day Robot
2024-08-29 11:32 ` |SUCCESS| pw143425 [PATCH] [v2] bus/pci: don't open uio device in se dpdklab
2024-08-29 11:40 ` dpdklab
2024-08-29 11:41 ` dpdklab
2024-08-29 11:49 ` dpdklab
2024-08-29 11:50 ` |PENDING| " dpdklab
2024-08-29 11:52 ` dpdklab
2024-08-29 11:54 ` |SUCCESS| " dpdklab
2024-08-29 11:55 ` dpdklab
2024-08-29 11:55 ` |PENDING| " dpdklab
2024-08-29 11:58 ` |SUCCESS| " dpdklab
2024-08-29 11:59 ` dpdklab
2024-08-29 12:01 ` dpdklab
2024-08-29 12:20 ` dpdklab
2024-08-29 12:20 ` dpdklab
2024-08-29 12:21 ` dpdklab
2024-08-29 12:45 ` dpdklab
2024-08-29 12:46 ` dpdklab
2024-08-29 12:46 ` dpdklab
2024-08-29 12:46 ` dpdklab
2024-08-29 12:48 ` dpdklab
2024-08-29 12:48 ` dpdklab
2024-08-29 12:50 ` dpdklab
2024-08-29 12:57 ` dpdklab
2024-08-29 13:05 ` dpdklab
2024-08-29 13:23 ` dpdklab
2024-08-29 13:26 ` dpdklab
2024-08-29 13:32 ` dpdklab
2024-08-29 13:37 ` dpdklab
2024-08-29 13:37 ` |PENDING| " dpdklab
2024-08-29 13:43 ` |SUCCESS| " dpdklab
2024-08-29 13:43 ` dpdklab
2024-08-29 13:45 ` dpdklab
2024-08-29 13:47 ` dpdklab
2024-08-29 13:47 ` dpdklab
2024-08-29 14:06 ` dpdklab
2024-08-29 14:18 ` dpdklab
2024-08-29 14:38 ` dpdklab
2024-08-29 14:38 ` dpdklab
2024-08-29 16:30 ` dpdklab
2024-09-19 13:07 ` dpdklab
2024-09-19 13:26 ` dpdklab
2024-09-19 13:39 ` dpdklab
2024-09-19 13:58 ` 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=202408290831.47T8VG4K2672070@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).