From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124452-124453 [PATCH v1 2/2] ethdev: pass structure pointer
Date: Thu, 23 Feb 2023 20:20:34 +0800 [thread overview]
Message-ID: <202302231220.31NCKYZ82878207@localhost.localdomain> (raw)
In-Reply-To: <20230223123029.2117781-3-adwivedi@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124453
_Compilation OK_
Submitter: Ankur Dwivedi <adwivedi@marvell.com>
Date: Thu, 23 Feb 2023 18:00:28 +0530
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 418f86c426f23ad3ffd397e69d19e8d6b5577e67
124452-124453 --> 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-23 12:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230223123029.2117781-3-adwivedi@marvell.com>
2023-02-23 12:20 ` qemudev [this message]
2023-02-23 12:24 ` qemudev
2023-02-23 12:31 ` |SUCCESS| pw124453 " checkpatch
2023-02-23 15:19 ` 0-day Robot
2023-02-23 16:36 |SUCCESS| pw124452-124453 [PATCH] [v1, " dpdklab
2023-02-23 16:40 dpdklab
2023-02-23 16:42 dpdklab
2023-02-23 16:43 dpdklab
2023-02-23 16:43 dpdklab
2023-02-23 16:52 dpdklab
2023-02-23 16:55 dpdklab
2023-02-23 17:04 dpdklab
2023-02-23 17:05 dpdklab
2023-02-23 17:12 dpdklab
2023-02-23 18:21 dpdklab
2023-02-23 18:27 dpdklab
2023-02-23 18:28 dpdklab
2023-02-23 18:43 dpdklab
2023-02-23 18:45 dpdklab
2023-02-23 18:54 dpdklab
2023-02-23 19:00 dpdklab
2023-02-23 19:02 dpdklab
2023-02-23 19:04 dpdklab
2023-02-23 19:07 dpdklab
2023-02-23 19:07 dpdklab
2023-02-23 19:09 dpdklab
2023-02-23 19:10 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=202302231220.31NCKYZ82878207@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).