From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123671-123675 [PATCH v2 5/5] eventdev: remove internal tracepoints from version map
Date: Fri, 10 Feb 2023 18:25:45 +0800 [thread overview]
Message-ID: <202302101025.31AAPjnq1531504@localhost.localdomain> (raw)
In-Reply-To: <20230210103446.1126999-6-adwivedi@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123675
_Compilation OK_
Submitter: Ankur Dwivedi <adwivedi@marvell.com>
Date: Fri, 10 Feb 2023 16:04:42 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 183bdfe224760b72d3cd44f5367c80b5ee073327
123671-123675 --> 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-10 10:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230210103446.1126999-6-adwivedi@marvell.com>
2023-02-10 10:25 ` qemudev [this message]
2023-02-10 10:29 ` qemudev
2023-02-10 10:36 ` |SUCCESS| pw123675 " checkpatch
2023-02-13 19:39 ` 0-day Robot
2023-02-15 15:19 |SUCCESS| pw123671-123675 [PATCH] [v2, " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-02-13 14:33 dpdklab
2023-02-12 22:04 dpdklab
2023-02-12 1:29 dpdklab
2023-02-12 1:29 dpdklab
2023-02-12 1:24 dpdklab
2023-02-12 1:16 dpdklab
2023-02-12 1:13 dpdklab
2023-02-12 1:10 dpdklab
2023-02-12 1:07 dpdklab
2023-02-12 1:03 dpdklab
2023-02-12 0:59 dpdklab
2023-02-12 0:57 dpdklab
2023-02-12 0:57 dpdklab
2023-02-12 0:53 dpdklab
2023-02-12 0:50 dpdklab
2023-02-12 0:35 dpdklab
2023-02-10 12:57 dpdklab
2023-02-10 11:21 dpdklab
2023-02-10 11:12 dpdklab
2023-02-10 11:11 dpdklab
2023-02-10 11:09 dpdklab
2023-02-10 11:08 dpdklab
2023-02-10 11:03 dpdklab
2023-02-10 10: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=202302101025.31AAPjnq1531504@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).