From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw133693 [PATCH v2] doc: update for Intel IPU
Date: Wed, 1 Nov 2023 10:07:24 +0800 [thread overview]
Message-ID: <202311010207.3A127OgX533277@localhost.localdomain> (raw)
In-Reply-To: <20231101103433.1234649-1-beilei.xing@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/133693
_Compilation OK_
Submitter: Xing, Beilei <beilei.xing@intel.com>
Date: Wed, 1 Nov 2023 10:34:33 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 6c14bc136c85194e27d9427e923c97b1e2c10211
133693 --> 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-11-01 2:28 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231101103433.1234649-1-beilei.xing@intel.com>
2023-11-01 2:07 ` qemudev [this message]
2023-11-01 2:11 ` qemudev
2023-11-01 2:16 ` checkpatch
2023-11-01 3:19 ` 0-day Robot
2023-11-01 5:52 |SUCCESS| pw133693 [PATCH] [v2] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-11-01 3:49 dpdklab
2023-11-01 3:38 dpdklab
2023-11-01 3:33 dpdklab
2023-11-01 3:14 dpdklab
2023-11-01 3:12 dpdklab
2023-11-01 3:11 dpdklab
2023-11-01 3:11 dpdklab
2023-11-01 3:11 dpdklab
2023-11-01 3:10 dpdklab
2023-11-01 3:10 dpdklab
2023-11-01 3:10 dpdklab
2023-11-01 3:10 dpdklab
2023-11-01 3:09 dpdklab
2023-11-01 3:09 dpdklab
2023-11-01 3:09 dpdklab
2023-11-01 3:09 dpdklab
2023-11-01 3:09 dpdklab
2023-11-01 3:08 dpdklab
2023-11-01 3:08 dpdklab
2023-11-01 3:08 dpdklab
2023-11-01 3:08 dpdklab
2023-11-01 3:08 dpdklab
2023-11-01 3:08 dpdklab
2023-11-01 3:08 dpdklab
2023-11-01 3:08 dpdklab
2023-11-01 3:08 dpdklab
2023-11-01 3:07 dpdklab
2023-11-01 3:07 dpdklab
2023-11-01 3:07 dpdklab
2023-11-01 3:07 dpdklab
2023-11-01 3:06 dpdklab
2023-11-01 3:06 dpdklab
2023-11-01 3:06 dpdklab
2023-11-01 3:06 dpdklab
2023-11-01 3:06 dpdklab
2023-11-01 3:06 dpdklab
2023-11-01 3:06 dpdklab
2023-11-01 3:05 dpdklab
2023-11-01 3:05 dpdklab
2023-11-01 3:05 dpdklab
2023-11-01 3:05 dpdklab
2023-11-01 3:00 dpdklab
2023-11-01 3:00 dpdklab
2023-11-01 3:00 dpdklab
2023-11-01 3:00 dpdklab
2023-11-01 2:59 dpdklab
2023-11-01 2:59 dpdklab
2023-11-01 2:59 dpdklab
2023-11-01 2:59 dpdklab
2023-11-01 2:58 dpdklab
2023-11-01 2:58 dpdklab
2023-11-01 2:57 dpdklab
2023-11-01 2:57 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=202311010207.3A127OgX533277@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).