From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124799-124800 [PATCH v4 2/2] devtools: add tracepoint check in checkpatch
Date: Mon, 6 Mar 2023 15:04:08 +0800 [thread overview]
Message-ID: <202303060704.326748B23956406@localhost.localdomain> (raw)
In-Reply-To: <20230303155811.2751210-3-adwivedi@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124800
_Compilation OK_
Submitter: Ankur Dwivedi <adwivedi@marvell.com>
Date: Fri, 3 Mar 2023 21:28:10 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 4ef69b2877a24ddb89afaf4bb6f4e73bb52a605b
124799-124800 --> 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-03-06 7:18 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230303155811.2751210-3-adwivedi@marvell.com>
2023-03-03 16:00 ` |SUCCESS| pw124800 " checkpatch
2023-03-03 17:59 ` 0-day Robot
2023-03-06 7:04 ` qemudev [this message]
2023-03-06 7:04 ` |SUCCESS| pw124799-124800 " qemudev
2023-03-03 18:33 |SUCCESS| pw124799-124800 [PATCH] [v4, " dpdklab
2023-03-03 18:34 dpdklab
2023-03-03 18:36 dpdklab
2023-03-03 18:39 dpdklab
2023-03-03 18:40 dpdklab
2023-03-03 18:43 dpdklab
2023-03-03 18:44 dpdklab
2023-03-03 18:46 dpdklab
2023-03-03 18:49 dpdklab
2023-03-03 18:50 dpdklab
2023-03-03 18:50 dpdklab
2023-03-03 19:03 dpdklab
2023-03-03 19:11 dpdklab
2023-03-03 19:44 dpdklab
2023-03-03 19:45 dpdklab
2023-03-03 19:46 dpdklab
2023-03-03 19:47 dpdklab
2023-03-03 19:51 dpdklab
2023-03-03 19:55 dpdklab
2023-03-03 19:59 dpdklab
2023-03-03 20:02 dpdklab
2023-03-03 20:09 dpdklab
2023-03-03 20:15 dpdklab
2023-03-03 20:22 dpdklab
2023-03-03 20:43 dpdklab
2023-03-04 2:07 dpdklab
2023-03-04 4:13 dpdklab
2023-03-04 8:59 dpdklab
2023-03-04 9:55 dpdklab
2023-03-04 10:54 dpdklab
2023-03-04 12:41 dpdklab
2023-03-05 8:33 dpdklab
2023-03-05 8:37 dpdklab
2023-03-05 8:41 dpdklab
2023-03-05 8:43 dpdklab
2023-03-05 8:43 dpdklab
2023-03-05 8:44 dpdklab
2023-03-05 8:46 dpdklab
2023-03-05 8:48 dpdklab
2023-03-05 8:59 dpdklab
2023-03-05 9:01 dpdklab
2023-03-05 9:03 dpdklab
2023-03-05 9:06 dpdklab
2023-03-05 9:06 dpdklab
2023-03-05 9:53 dpdklab
2023-03-05 10:01 dpdklab
2023-03-05 10:05 dpdklab
2023-03-05 10:08 dpdklab
2023-03-05 10:10 dpdklab
2023-03-05 10:15 dpdklab
2023-03-05 10:17 dpdklab
2023-03-05 10:19 dpdklab
2023-03-05 10:20 dpdklab
2023-03-05 10:21 dpdklab
2023-03-05 10:25 dpdklab
2023-03-05 10:28 dpdklab
2023-03-05 10:45 dpdklab
2023-03-05 10:45 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=202303060704.326748B23956406@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).