From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122696-122695 [PATCH v2 2/2] ethdev: introduce the PHY affinity field in Tx queue API
Date: Tue, 31 Jan 2023 00:57:02 +0800 [thread overview]
Message-ID: <202301301657.30UGv2WA2765700@localhost.localdomain> (raw)
In-Reply-To: <20230130170041.1360-3-jiaweiw@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/122695
_Compilation OK_
Submitter: Jiawei Wang <jiaweiw@nvidia.com>
Date: Mon, 30 Jan 2023 19:00:39 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 2a211079a92e962bbd0ec81e425a6ffc32890e67
122696-122695 --> 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-01-30 17:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230130170041.1360-3-jiaweiw@nvidia.com>
2023-01-30 16:57 ` qemudev [this message]
2023-01-30 17:01 ` qemudev
2023-01-30 17:02 ` |SUCCESS| pw122695 " checkpatch
2023-01-30 17:59 ` |FAILURE| " 0-day Robot
2023-01-30 17:30 |SUCCESS| pw122696-122695 [PATCH] [v2, " dpdklab
2023-01-30 17:34 dpdklab
2023-01-30 17:34 dpdklab
2023-01-30 17:36 dpdklab
2023-01-30 17:37 dpdklab
2023-01-30 17:42 dpdklab
2023-01-30 17:46 dpdklab
2023-01-30 17:50 dpdklab
2023-01-30 18:56 dpdklab
2023-01-30 19:58 dpdklab
2023-01-30 21:51 dpdklab
2023-01-30 22:14 dpdklab
2023-01-30 22:18 dpdklab
2023-01-30 22:18 dpdklab
2023-01-30 22:23 dpdklab
2023-01-30 22:23 dpdklab
2023-01-30 22:23 dpdklab
2023-01-30 22:23 dpdklab
2023-01-30 22:24 dpdklab
2023-01-30 22:25 dpdklab
2023-01-30 22:25 dpdklab
2023-01-30 22:26 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=202301301657.30UGv2WA2765700@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).