From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124551-124552 [PATCH 2/2] net/mlx5: fix isolated mode when repr matching is disabled
Date: Sun, 26 Feb 2023 04:08:04 +0800 [thread overview]
Message-ID: <202302252008.31PK84aA4063917@localhost.localdomain> (raw)
In-Reply-To: <20230225201810.10838-3-dsosnowski@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124552
_Compilation OK_
Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Sat, 25 Feb 2023 20:18:09 +0000
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 34c8d1d3bef546f03159407a7af314176456d629
124551-124552 --> 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-02-25 20:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230225201810.10838-3-dsosnowski@nvidia.com>
2023-02-25 20:08 ` qemudev [this message]
2023-02-25 20:12 ` qemudev
2023-02-25 20:20 ` |SUCCESS| pw124552 " checkpatch
2023-02-25 23:19 ` 0-day Robot
2023-02-27 16:16 |SUCCESS| pw124551-124552 [PATCH] [2/2] " dpdklab
2023-02-27 16:40 dpdklab
2023-02-27 16:51 dpdklab
2023-02-27 16:52 dpdklab
2023-02-27 16:55 dpdklab
2023-02-27 16:59 dpdklab
2023-02-27 17:00 dpdklab
2023-02-27 17:08 dpdklab
2023-02-27 17:15 dpdklab
2023-02-27 17:28 dpdklab
2023-02-27 17:35 dpdklab
2023-02-27 18:53 dpdklab
2023-02-27 18:59 dpdklab
2023-02-27 19:06 dpdklab
2023-02-27 19:07 dpdklab
2023-02-27 19:08 dpdklab
2023-02-27 19:08 dpdklab
2023-02-27 19:11 dpdklab
2023-02-27 19:14 dpdklab
2023-02-27 19:19 dpdklab
2023-02-27 19:24 dpdklab
2023-02-27 19:24 dpdklab
2023-02-27 19:26 dpdklab
2023-02-27 19:28 dpdklab
2023-02-27 19:28 dpdklab
2023-02-27 22:04 dpdklab
2023-02-27 23: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=202302252008.31PK84aA4063917@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).