From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw133854 [PATCH] raw/cnxk_gpio: switch to dynamic logging
Date: Sat, 4 Nov 2023 04:51:41 +0800 [thread overview]
Message-ID: <202311032051.3A3Kpfdp3878615@localhost.localdomain> (raw)
In-Reply-To: <20231103210952.2447882-1-tduszynski@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/133854
_Compilation OK_
Submitter: Tomasz Duszynski <tduszynski@marvell.com>
Date: Fri, 3 Nov 2023 22:09:52 +0100
DPDK git baseline: Repo:dpdk-next-net-mrvl
Branch: for-next-net
CommitID: 84b6256087af629c76cb879a8ecfbe36039ce3fb
133854 --> 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-11-03 21:12 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231103210952.2447882-1-tduszynski@marvell.com>
2023-11-03 20:51 ` qemudev [this message]
2023-11-03 20:56 ` qemudev
2023-11-03 21:11 ` checkpatch
2023-11-03 22:20 ` 0-day Robot
2023-11-03 23:29 dpdklab
2023-11-03 23:30 dpdklab
2023-11-03 23:30 dpdklab
2023-11-03 23:31 dpdklab
2023-11-03 23:31 dpdklab
2023-11-03 23:32 dpdklab
2023-11-03 23:32 dpdklab
2023-11-03 23:33 dpdklab
2023-11-03 23:33 dpdklab
2023-11-03 23:35 dpdklab
2023-11-03 23:39 dpdklab
2023-11-03 23:53 dpdklab
2023-11-03 23:53 dpdklab
2023-11-03 23:53 dpdklab
2023-11-03 23:53 dpdklab
2023-11-03 23:57 dpdklab
2023-11-03 23:57 dpdklab
2023-11-03 23:57 dpdklab
2023-11-03 23:57 dpdklab
2023-11-03 23:57 dpdklab
2023-11-03 23:57 dpdklab
2023-11-03 23:57 dpdklab
2023-11-03 23:57 dpdklab
2023-11-03 23:57 dpdklab
2023-11-03 23:57 dpdklab
2023-11-03 23:58 dpdklab
2023-11-03 23:58 dpdklab
2023-11-04 0:00 dpdklab
2023-11-04 0:02 dpdklab
2023-11-04 0:02 dpdklab
2023-11-04 0:02 dpdklab
2023-11-04 0:02 dpdklab
2023-11-04 0:02 dpdklab
2023-11-04 0:02 dpdklab
2023-11-04 0:06 dpdklab
2023-11-04 0:07 dpdklab
2023-11-04 0:07 dpdklab
2023-11-04 0:08 dpdklab
2023-11-04 0:11 dpdklab
2023-11-04 0:23 dpdklab
2023-11-04 0:28 dpdklab
2023-11-04 0:31 dpdklab
2023-11-04 0:31 dpdklab
2023-11-04 0:37 dpdklab
2023-11-04 0:39 dpdklab
2023-11-04 0:39 dpdklab
2023-11-04 0:41 dpdklab
2023-11-04 0:48 dpdklab
2023-11-04 0:55 dpdklab
2023-11-04 0:59 dpdklab
2023-11-04 1:10 dpdklab
2023-11-04 2:39 dpdklab
2023-11-04 4:14 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=202311032051.3A3Kpfdp3878615@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).