From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw143050 [PATCH] log: allow log register API to update log level
Date: Fri, 9 Aug 2024 20:35:45 +0800 [thread overview]
Message-ID: <202408091235.479CZj6p4037823@localhost.localdomain> (raw)
In-Reply-To: <20240809130149.363053-1-bharathpaul@gmail.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/143050
_Compilation OK_
Submitter: Bharath Paulraj <bharathpaul@gmail.com>
Date: Fri, 9 Aug 2024 15:01:49 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: cb9187bc5c2b4bab0ad80194ac3b60491de14e8c
143050 --> 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-08-09 13:04 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240809130149.363053-1-bharathpaul@gmail.com>
2024-08-09 12:35 ` qemudev [this message]
2024-08-09 12:40 ` qemudev
2024-08-09 13:02 ` checkpatch
2024-08-09 14:03 ` 0-day Robot
2024-08-09 14:52 ` |SUCCESS| pw143050 [PATCH] log: allow log register API to update log dpdklab
2024-08-09 14:54 ` dpdklab
2024-08-09 14:56 ` dpdklab
2024-08-09 15:15 ` dpdklab
2024-08-09 15:16 ` |PENDING| " dpdklab
2024-08-09 15:23 ` |SUCCESS| " dpdklab
2024-08-09 15:58 ` dpdklab
2024-08-09 16:13 ` dpdklab
2024-08-09 16:30 ` dpdklab
2024-08-09 17:33 ` |WARNING| " dpdklab
2024-08-09 18:00 ` dpdklab
2024-08-09 18:00 ` dpdklab
2024-08-09 18:03 ` dpdklab
2024-08-09 18:12 ` dpdklab
2024-08-09 18:14 ` dpdklab
2024-08-09 18:14 ` dpdklab
2024-08-09 18:25 ` dpdklab
2024-08-09 18:27 ` dpdklab
2024-08-09 18:28 ` |SUCCESS| " dpdklab
2024-08-09 18:41 ` |WARNING| " dpdklab
2024-08-09 18:45 ` dpdklab
2024-08-09 18:47 ` |SUCCESS| " dpdklab
2024-08-09 18:52 ` dpdklab
2024-08-09 21:12 ` |PENDING| " dpdklab
2024-08-09 21:27 ` dpdklab
2024-08-09 21:28 ` dpdklab
2024-08-09 21:30 ` dpdklab
2024-08-09 21:32 ` |SUCCESS| " dpdklab
2024-08-09 21:34 ` dpdklab
2024-08-09 21:38 ` |PENDING| " dpdklab
2024-08-09 22:06 ` dpdklab
2024-08-09 22:17 ` dpdklab
2024-08-09 22:18 ` |SUCCESS| " dpdklab
2024-08-09 22:18 ` |PENDING| " dpdklab
2024-08-09 22:50 ` dpdklab
2024-08-09 22:54 ` dpdklab
2024-08-09 22:55 ` dpdklab
2024-08-09 23:16 ` dpdklab
2024-08-09 23:17 ` dpdklab
2024-08-09 23:17 ` dpdklab
2024-08-09 23:17 ` dpdklab
2024-08-09 23:44 ` dpdklab
2024-08-09 23:58 ` dpdklab
2024-08-10 0:07 ` dpdklab
2024-08-10 0:30 ` dpdklab
2024-08-10 3:58 ` |SUCCESS| " dpdklab
2024-08-10 16:39 ` |PENDING| " 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=202408091235.479CZj6p4037823@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).