From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124546 [PATCH v1 1/1] doc: update to Intel vRAN Boost PMD
Date: Sat, 25 Feb 2023 02:13:56 +0800 [thread overview]
Message-ID: <202302241813.31OIDukb3857920@localhost.localdomain> (raw)
In-Reply-To: <20230224182019.83342-2-nicolas.chautru@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124546
_Compilation OK_
Submitter: Nicolas Chautru <nicolas.chautru@intel.com>
Date: Fri, 24 Feb 2023 18:20:19 +0000
DPDK git baseline: Repo:dpdk-next-baseband
Branch: for-main
CommitID: 3ba3030b4fab3f31fd7c22dc24c7b83f0404811a
124546 --> 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-02-24 18:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230224182019.83342-2-nicolas.chautru@intel.com>
2023-02-24 18:13 ` qemudev [this message]
2023-02-24 18:17 ` qemudev
2023-02-24 18:25 ` |WARNING| " checkpatch
2023-02-24 20:59 ` |SUCCESS| " 0-day Robot
2023-02-24 19:07 |SUCCESS| pw124546 [PATCH] [v1, " dpdklab
2023-02-24 19:07 dpdklab
2023-02-24 19:11 dpdklab
2023-02-24 19:13 dpdklab
2023-02-24 19:18 dpdklab
2023-02-24 19:22 dpdklab
2023-02-24 19:26 dpdklab
2023-02-24 19:27 dpdklab
2023-02-24 19:33 dpdklab
2023-02-24 19:40 dpdklab
2023-02-24 20:56 dpdklab
2023-02-24 21:38 dpdklab
2023-02-24 21:42 dpdklab
2023-02-24 21:48 dpdklab
2023-02-24 21:50 dpdklab
2023-02-24 21:51 dpdklab
2023-02-24 21:53 dpdklab
2023-02-24 21:54 dpdklab
2023-02-24 21:54 dpdklab
2023-02-24 21:55 dpdklab
2023-02-24 21:56 dpdklab
2023-02-24 21:58 dpdklab
2023-02-24 21:58 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=202302241813.31OIDukb3857920@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).