From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw127357 [PATCH] pci: add O_CLOEXEC when open uio device
Date: Thu, 25 May 2023 10:49:54 +0800 [thread overview]
Message-ID: <202305250249.34P2nsgu3513834@localhost.localdomain> (raw)
In-Reply-To: <20230525030035.33872-1-suweifeng1@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/127357
_Compilation OK_
Submitter: Weifeng Su <suweifeng1@huawei.com>
Date: Thu, 25 May 2023 11:00:35 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 2d9e10932d535ea553081b489a25f6fce7ec7996
127357 --> 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:[~2023-05-25 3:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230525030035.33872-1-suweifeng1@huawei.com>
2023-05-25 2:49 ` qemudev [this message]
2023-05-25 2:53 ` |FAILURE| " qemudev
2023-05-25 3:01 ` |WARNING| " checkpatch
2023-05-25 4:44 ` |SUCCESS| " 0-day Robot
2023-05-25 14:58 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-05-25 5:10 dpdklab
2023-05-25 4:57 dpdklab
2023-05-25 4:43 dpdklab
2023-05-25 4:30 dpdklab
2023-05-25 4:29 dpdklab
2023-05-25 4:27 dpdklab
2023-05-25 4:21 dpdklab
2023-05-25 4:20 dpdklab
2023-05-25 4:20 dpdklab
2023-05-25 4:20 dpdklab
2023-05-25 4:20 dpdklab
2023-05-25 4:15 dpdklab
2023-05-25 4:11 dpdklab
2023-05-25 4:11 dpdklab
2023-05-25 4:07 dpdklab
2023-05-25 4:06 dpdklab
2023-05-25 3:55 dpdklab
2023-05-25 3:48 dpdklab
2023-05-25 3:48 dpdklab
2023-05-25 3:47 dpdklab
2023-05-25 3:46 dpdklab
2023-05-25 3:46 dpdklab
2023-05-25 3:42 dpdklab
2023-05-25 3:40 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=202305250249.34P2nsgu3513834@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).