From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw129041 [PATCH] doc: update release notes for Intel IPU
Date: Wed, 28 Jun 2023 15:11:12 +0800 [thread overview]
Message-ID: <202306280711.35S7BCI32934034@localhost.localdomain> (raw)
In-Reply-To: <20230628153857.112825-1-beilei.xing@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/129041
_Compilation OK_
Submitter: Xing, Beilei <beilei.xing@intel.com>
Date: Wed, 28 Jun 2023 15:38:57 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 93a4b3beba4ee611685148917981f846427cafb2
129041 --> 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-06-28 7:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230628153857.112825-1-beilei.xing@intel.com>
2023-06-28 7:11 ` qemudev [this message]
2023-06-28 7:15 ` qemudev
2023-06-28 7:22 ` checkpatch
2023-06-28 8:21 ` 0-day Robot
2023-06-28 8:36 dpdklab
2023-06-28 8:36 dpdklab
2023-06-28 8:37 dpdklab
2023-06-28 8:37 dpdklab
2023-06-28 8:37 dpdklab
2023-06-28 8:38 dpdklab
2023-06-28 8:38 dpdklab
2023-06-28 9:03 dpdklab
2023-06-28 9:10 dpdklab
2023-06-28 9:10 dpdklab
2023-06-28 9:17 dpdklab
2023-06-28 9:25 dpdklab
2023-06-28 9:25 dpdklab
2023-06-28 9:29 dpdklab
2023-06-28 9:29 dpdklab
2023-06-28 9:31 dpdklab
2023-06-28 9:33 dpdklab
2023-06-28 9:40 dpdklab
2023-06-28 9:40 dpdklab
2023-06-28 11:02 dpdklab
2023-06-28 11:03 dpdklab
2023-06-28 13:51 dpdklab
2023-06-28 14:07 dpdklab
2023-06-28 14:11 dpdklab
2023-06-28 14:22 dpdklab
2023-06-28 14:26 dpdklab
2023-06-28 18:56 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=202306280711.35S7BCI32934034@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).