From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139621-139624 [PATCH v1 5/5] baseband/acc: cosmetic log changes
Date: Mon, 22 Apr 2024 23:19:50 +0800 [thread overview]
Message-ID: <202404221519.43MFJogb681767@localhost.localdomain> (raw)
In-Reply-To: <20240422154008.119800-6-hernan.vargas@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139624
_Compilation OK_
Submitter: Hernan Vargas <hernan.vargas@intel.com>
Date: Mon, 22 Apr 2024 08:40:04 -0700
DPDK git baseline: Repo:dpdk-next-baseband
Branch: for-main
CommitID: 98b4ecb4e4d73e93fdfa53f552b48d71104b445f
139621-139624 --> 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:[~2024-04-22 15:47 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240422154008.119800-6-hernan.vargas@intel.com>
2024-04-22 15:19 ` qemudev [this message]
2024-04-22 15:24 ` qemudev
2024-04-22 15:45 ` |SUCCESS| pw139624 " checkpatch
2024-04-22 16:45 ` 0-day Robot
2024-04-22 19:31 ` |SUCCESS| pw139621-139624 [PATCH] [v1,5/5] baseband/acc: cosmetic lo dpdklab
2024-04-22 19:32 ` dpdklab
2024-04-22 19:32 ` dpdklab
2024-04-22 19:43 ` dpdklab
2024-04-22 19:44 ` dpdklab
2024-04-22 19:47 ` dpdklab
2024-04-22 19:47 ` dpdklab
2024-04-22 19:51 ` dpdklab
2024-04-22 19:51 ` dpdklab
2024-04-22 19:54 ` dpdklab
2024-04-22 19:55 ` dpdklab
2024-04-22 19:56 ` dpdklab
2024-04-22 19:56 ` dpdklab
2024-04-22 19:57 ` dpdklab
2024-04-22 20:02 ` dpdklab
2024-04-22 20:02 ` dpdklab
2024-04-22 20:03 ` dpdklab
2024-04-22 20:06 ` dpdklab
2024-04-22 20:17 ` dpdklab
2024-04-22 20:19 ` dpdklab
2024-04-22 20:19 ` dpdklab
2024-04-22 20:37 ` dpdklab
2024-04-22 20:46 ` dpdklab
2024-04-22 20:46 ` dpdklab
2024-04-22 20:47 ` dpdklab
2024-04-22 20:48 ` dpdklab
2024-04-22 20:49 ` dpdklab
2024-04-22 20:50 ` dpdklab
2024-04-22 20:50 ` dpdklab
2024-04-22 20:50 ` dpdklab
2024-04-22 20:51 ` dpdklab
2024-04-22 20:51 ` dpdklab
2024-04-22 20:53 ` dpdklab
2024-04-22 20:53 ` dpdklab
2024-04-22 20:53 ` dpdklab
2024-04-22 20:54 ` dpdklab
2024-04-22 20:54 ` dpdklab
2024-04-22 20:56 ` dpdklab
2024-04-22 20:56 ` dpdklab
2024-04-22 20:57 ` dpdklab
2024-04-22 20:58 ` dpdklab
2024-04-22 20:59 ` dpdklab
2024-04-22 20:59 ` dpdklab
2024-04-22 21:02 ` dpdklab
2024-04-22 21:03 ` dpdklab
2024-04-22 21:03 ` dpdklab
2024-04-22 21:04 ` dpdklab
2024-04-22 21:04 ` dpdklab
2024-04-22 21:04 ` dpdklab
2024-04-22 21:04 ` dpdklab
2024-04-22 21:04 ` dpdklab
2024-04-22 21:05 ` dpdklab
2024-04-22 21:05 ` dpdklab
2024-04-22 21:05 ` dpdklab
2024-04-22 21:05 ` dpdklab
2024-04-22 21:06 ` dpdklab
2024-04-22 21:06 ` dpdklab
2024-04-22 21:06 ` dpdklab
2024-04-22 21:06 ` dpdklab
2024-04-22 21:07 ` dpdklab
2024-04-22 21:07 ` dpdklab
2024-04-22 21:07 ` dpdklab
2024-04-22 21:07 ` dpdklab
2024-04-22 21:10 ` dpdklab
2024-04-22 21:13 ` dpdklab
2024-04-22 21:13 ` dpdklab
2024-04-22 21:14 ` dpdklab
2024-04-22 21:26 ` dpdklab
2024-04-22 21:39 ` dpdklab
2024-04-22 21:41 ` dpdklab
2024-04-22 21:42 ` dpdklab
2024-04-22 21:42 ` dpdklab
2024-04-22 21:43 ` dpdklab
2024-04-22 21:43 ` dpdklab
2024-04-22 21:44 ` dpdklab
2024-04-22 21:45 ` dpdklab
2024-04-22 21:46 ` dpdklab
2024-04-22 21:48 ` dpdklab
2024-04-22 21:49 ` dpdklab
2024-04-22 21:54 ` dpdklab
2024-04-22 21:56 ` dpdklab
2024-04-22 21:58 ` dpdklab
2024-04-22 22:01 ` dpdklab
2024-04-22 22:02 ` dpdklab
2024-04-22 22:02 ` dpdklab
2024-04-22 22:02 ` dpdklab
2024-04-22 22:08 ` dpdklab
2024-04-22 22:54 ` dpdklab
2024-04-23 0:02 ` 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=202404221519.43MFJogb681767@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).