From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126444 [PATCH v5] common/idpf: refine capability get
Date: Mon, 24 Apr 2023 16:21:11 +0800 [thread overview]
Message-ID: <202304240821.33O8LBuN796215@localhost.localdomain> (raw)
In-Reply-To: <20230424080822.13541-1-beilei.xing@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126444
_Compilation OK_
Submitter: Xing, Beilei <beilei.xing@intel.com>
Date: Mon, 24 Apr 2023 08:08:22 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: f649fd010f2dd3a97e15f2ef106440a79f6c95fb
126444 --> 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-04-24 10:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230424080822.13541-1-beilei.xing@intel.com>
2023-04-24 8:21 ` qemudev [this message]
2023-04-24 8:25 ` qemudev
2023-04-24 8:32 ` checkpatch
2023-04-24 9:19 ` 0-day Robot
2023-04-24 20:37 |SUCCESS| pw126444 [PATCH] [v5] " dpdklab
2023-04-24 20:39 dpdklab
2023-04-24 20:42 dpdklab
2023-04-24 20:43 dpdklab
2023-04-24 20:43 dpdklab
2023-04-24 20:46 dpdklab
2023-04-24 20:47 dpdklab
2023-04-24 20:49 dpdklab
2023-04-24 20:54 dpdklab
2023-04-24 20:55 dpdklab
2023-04-24 20:59 dpdklab
2023-04-24 21:07 dpdklab
2023-04-24 21:54 dpdklab
2023-04-24 21:54 dpdklab
2023-04-24 21:54 dpdklab
2023-04-24 21:56 dpdklab
2023-04-24 21:58 dpdklab
2023-04-24 21:58 dpdklab
2023-04-24 21:59 dpdklab
2023-04-24 22:03 dpdklab
2023-04-24 22:12 dpdklab
2023-04-24 22:18 dpdklab
2023-04-24 23:14 dpdklab
2023-04-24 23:18 dpdklab
2023-04-25 0:36 dpdklab
2023-04-25 0:37 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=202304240821.33O8LBuN796215@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).