From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw145758 [PATCH v3] bus/pci: don't open uio device in secondary process
Date: Fri, 11 Oct 2024 18:49:08 +0800 [thread overview]
Message-ID: <202410111049.49BAn84H3980041@localhost.localdomain> (raw)
In-Reply-To: <20241011111533.20746-1-konrad.sztyber@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/145758
_Compilation OK_
Submitter: Konrad Sztyber <konrad.sztyber@intel.com>
Date: Fri, 11 Oct 2024 13:15:05 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 93f8d73ac18de2df963698d31d8dd819392deade
145758 --> 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-10-11 11:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241011111533.20746-1-konrad.sztyber@intel.com>
2024-10-11 10:49 ` qemudev [this message]
2024-10-11 10:53 ` qemudev
2024-10-11 11:17 ` |WARNING| " checkpatch
2024-10-11 12:03 ` |SUCCESS| " 0-day Robot
2024-10-11 19:37 ` |PENDING| pw145758 [PATCH] [v3] bus/pci: don't open uio device in se dpdklab
2024-10-11 19:46 ` |SUCCESS| " dpdklab
2024-10-11 20:32 ` |PENDING| " dpdklab
2024-10-11 23:57 ` dpdklab
2024-10-12 0:13 ` |FAILURE| " dpdklab
2024-10-12 1:39 ` |PENDING| " dpdklab
2024-10-12 4:10 ` |SUCCESS| " dpdklab
2024-10-12 4:30 ` dpdklab
2024-10-12 19:42 ` dpdklab
2024-10-21 8:56 ` dpdklab
2024-10-23 5:42 ` dpdklab
2024-10-24 13:01 ` dpdklab
2024-10-24 13:05 ` dpdklab
2024-10-24 13:11 ` dpdklab
2024-10-24 13:13 ` dpdklab
2024-10-24 13:37 ` dpdklab
2024-10-25 8:13 ` dpdklab
2024-10-25 8:48 ` 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=202410111049.49BAn84H3980041@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).