From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126655 [PATCH] eventdev/eth_tx: fix runtime parameter set API
Date: Tue, 2 May 2023 18:00:10 +0800 [thread overview]
Message-ID: <202305021000.342A0AKw3432189@localhost.localdomain> (raw)
In-Reply-To: <20230502053613.1131362-1-s.v.naga.harish.k@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126655
_Compilation OK_
Submitter: Naga Harish K S V <s.v.naga.harish.k@intel.com>
Date: Tue, 2 May 2023 00:36:13 -0500
DPDK git baseline: Repo:dpdk-next-eventdev
Branch: for-main
CommitID: d8e842a79c9198186b2e44d7a8333b71159d5da3
126655 --> 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 prev parent reply other threads:[~2023-05-02 10:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230502053613.1131362-1-s.v.naga.harish.k@intel.com>
2023-05-02 5:37 ` checkpatch
2023-05-02 10:00 ` qemudev [this message]
2023-05-02 10:04 ` qemudev
2023-05-02 6:50 dpdklab
2023-05-02 6:55 dpdklab
2023-05-02 6:57 dpdklab
2023-05-02 6:57 dpdklab
2023-05-02 6:58 dpdklab
2023-05-02 7:01 dpdklab
2023-05-02 7:10 dpdklab
2023-05-02 7:19 dpdklab
2023-05-02 7:19 dpdklab
2023-05-02 7:23 dpdklab
2023-05-02 7:24 dpdklab
2023-05-02 7:24 dpdklab
2023-05-02 7:29 dpdklab
2023-05-02 7:30 dpdklab
2023-05-02 7:30 dpdklab
2023-05-02 7:31 dpdklab
2023-05-02 7:32 dpdklab
2023-05-02 7:37 dpdklab
2023-05-02 7:52 dpdklab
2023-05-02 8:39 dpdklab
2023-05-02 8:42 dpdklab
2023-05-02 10:37 dpdklab
2023-05-02 10: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=202305021000.342A0AKw3432189@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).