From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124436 [PATCH] common/idpf: fix Rx queue configuration
Date: Thu, 23 Feb 2023 11:34:53 +0800 [thread overview]
Message-ID: <202302230334.31N3Yrvh2650153@localhost.localdomain> (raw)
In-Reply-To: <20230223031646.11222-1-beilei.xing@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124436
_Compilation OK_
Submitter: Xing, Beilei <beilei.xing@intel.com>
Date: Thu, 23 Feb 2023 03:16:46 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 57ad1ebbe8ae7684b7a83e2eb5cc1a7613b400ca
124436 --> 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-23 3:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230223031646.11222-1-beilei.xing@intel.com>
2023-02-23 3:34 ` qemudev [this message]
2023-02-23 3:38 ` qemudev
2023-02-23 3:46 ` checkpatch
2023-02-23 6:39 ` 0-day Robot
2023-02-23 4:15 dpdklab
2023-02-23 4:18 dpdklab
2023-02-23 4:19 dpdklab
2023-02-23 4:22 dpdklab
2023-02-23 4:31 dpdklab
2023-02-23 4:34 dpdklab
2023-02-23 4:35 dpdklab
2023-02-23 4:36 dpdklab
2023-02-23 4:43 dpdklab
2023-02-23 4:56 dpdklab
2023-02-23 6:48 dpdklab
2023-02-23 6:58 dpdklab
2023-02-23 7:02 dpdklab
2023-02-23 7:03 dpdklab
2023-02-23 7:08 dpdklab
2023-02-23 7:09 dpdklab
2023-02-23 7:13 dpdklab
2023-02-23 7:14 dpdklab
2023-02-23 7:16 dpdklab
2023-02-23 7:18 dpdklab
2023-02-23 7:20 dpdklab
2023-02-23 7:26 dpdklab
2023-02-23 7:26 dpdklab
2023-02-23 10:40 dpdklab
2023-02-24 20:39 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=202302230334.31N3Yrvh2650153@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).