From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw134126 [PATCH] net/mlx5/hws: fix typo in the log
Date: Mon, 13 Nov 2023 15:02:33 +0800 [thread overview]
Message-ID: <202311130702.3AD72X9C1247355@localhost.localdomain> (raw)
In-Reply-To: <20231113072051.6748-1-bingz@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/134126
_Compilation OK_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Mon, 13 Nov 2023 09:20:51 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 57b791c357f0fcbfb4a6d9336374c509c1c1c7e9
134126 --> 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-13 7:23 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231113072051.6748-1-bingz@nvidia.com>
2023-11-13 7:02 ` qemudev [this message]
2023-11-13 7:06 ` qemudev
2023-11-13 7:22 ` checkpatch
2023-11-13 8:39 ` 0-day Robot
2023-11-13 9:36 dpdklab
2023-11-13 9:37 dpdklab
2023-11-13 9:51 dpdklab
2023-11-13 9:57 dpdklab
2023-11-13 10:00 dpdklab
2023-11-13 10:01 dpdklab
2023-11-13 10:03 dpdklab
2023-11-13 10:04 dpdklab
2023-11-13 10:05 dpdklab
2023-11-13 10:18 dpdklab
2023-11-13 10:19 dpdklab
2023-11-13 10:20 dpdklab
2023-11-13 10:20 dpdklab
2023-11-13 10:20 dpdklab
2023-11-13 10:21 dpdklab
2023-11-13 10:21 dpdklab
2023-11-13 10:22 dpdklab
2023-11-13 10:22 dpdklab
2023-11-13 10:22 dpdklab
2023-11-13 10:22 dpdklab
2023-11-13 10:22 dpdklab
2023-11-13 10:22 dpdklab
2023-11-13 10:23 dpdklab
2023-11-13 10:23 dpdklab
2023-11-13 10:23 dpdklab
2023-11-13 10:23 dpdklab
2023-11-13 10:24 dpdklab
2023-11-13 10:24 dpdklab
2023-11-13 10:24 dpdklab
2023-11-13 10:25 dpdklab
2023-11-13 10:25 dpdklab
2023-11-13 10:25 dpdklab
2023-11-13 10:26 dpdklab
2023-11-13 10:26 dpdklab
2023-11-13 10:26 dpdklab
2023-11-13 10:26 dpdklab
2023-11-13 10:26 dpdklab
2023-11-13 10:28 dpdklab
2023-11-13 10:30 dpdklab
2023-11-13 10:30 dpdklab
2023-11-13 10:31 dpdklab
2023-11-13 10:32 dpdklab
2023-11-13 10:33 dpdklab
2023-11-13 10:34 dpdklab
2023-11-13 10:35 dpdklab
2023-11-13 10:36 dpdklab
2023-11-13 10:41 dpdklab
2023-11-13 10:42 dpdklab
2023-11-13 10:43 dpdklab
2023-11-13 10:45 dpdklab
2023-11-13 10:51 dpdklab
2023-11-13 12:45 dpdklab
2023-11-13 13:25 dpdklab
2023-11-15 10:38 dpdklab
2023-11-15 11:17 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=202311130702.3AD72X9C1247355@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).