From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw145136-145145 [PATCH 10/10] ethdev: require checking results of info_get functions
Date: Sat, 5 Oct 2024 00:00:38 +0800 [thread overview]
Message-ID: <202410041600.494G0cHq473746@localhost.localdomain> (raw)
In-Reply-To: <20241004162418.52940-11-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/145145
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Fri, 4 Oct 2024 09:21:48 -0700
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 0107bd57c612a3b8b6aab6e5ae761bad3a9c2b1e
145136-145145 --> 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-04 16:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241004162418.52940-11-stephen@networkplumber.org>
2024-10-04 16:00 ` qemudev [this message]
2024-10-04 16:04 ` qemudev
2024-10-04 16:26 ` |SUCCESS| pw145145 " checkpatch
2024-10-04 17:23 ` 0-day Robot
2024-10-05 1:14 ` |PENDING| pw145136-145145 [PATCH] [10/10] ethdev: require checking r dpdklab
2024-10-05 1:20 ` |SUCCESS| " dpdklab
2024-10-05 1:41 ` dpdklab
2024-10-05 1:44 ` dpdklab
2024-10-05 1:46 ` dpdklab
2024-10-05 1:46 ` dpdklab
2024-10-05 2:05 ` |PENDING| " dpdklab
2024-10-05 2:28 ` dpdklab
2024-10-05 2:30 ` |SUCCESS| " dpdklab
2024-10-05 3:45 ` dpdklab
2024-10-05 3:53 ` dpdklab
2024-10-05 4:00 ` dpdklab
2024-10-05 4:09 ` |PENDING| " dpdklab
2024-10-05 4:16 ` |SUCCESS| " dpdklab
2024-10-05 4:20 ` dpdklab
2024-10-05 6:35 ` dpdklab
2024-10-05 6:40 ` dpdklab
2024-10-05 7:54 ` dpdklab
2024-10-05 17: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=202410041600.494G0cHq473746@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).