From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126067-126071 [PATCH v2 5/5] net/cpfl: fix Rx data buffer size
Date: Fri, 14 Apr 2023 13:37:19 +0800 [thread overview]
Message-ID: <202304140537.33E5bJK7582469@localhost.localdomain> (raw)
In-Reply-To: <20230414054744.1399735-6-wenjun1.wu@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126071
_Compilation OK_
Submitter: Wenjun Wu <wenjun1.wu@intel.com>
Date: Fri, 14 Apr 2023 13:47:40 +0800
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 3bc3d9f9f3df2e22c3958d1a3dac68ce2d708b33
126067-126071 --> 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-04-14 5:51 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230414054744.1399735-6-wenjun1.wu@intel.com>
2023-04-14 5:37 ` qemudev [this message]
2023-04-14 5:41 ` qemudev
2023-04-14 5:48 ` |SUCCESS| pw126071 " checkpatch
2023-04-14 6:59 ` 0-day Robot
2023-04-14 8:31 |SUCCESS| pw126067-126071 [PATCH] [v2, " dpdklab
2023-04-14 8:32 dpdklab
2023-04-14 8:36 dpdklab
2023-04-14 8:37 dpdklab
2023-04-14 8:39 dpdklab
2023-04-14 8:40 dpdklab
2023-04-14 8:43 dpdklab
2023-04-14 8:44 dpdklab
2023-04-14 8:52 dpdklab
2023-04-14 8:56 dpdklab
2023-04-14 9:13 dpdklab
2023-04-14 9:24 dpdklab
2023-04-14 9:25 dpdklab
2023-04-14 9:30 dpdklab
2023-04-14 9:30 dpdklab
2023-04-14 9:31 dpdklab
2023-04-14 9:32 dpdklab
2023-04-14 9:37 dpdklab
2023-04-14 9:37 dpdklab
2023-04-14 9:47 dpdklab
2023-04-14 9:50 dpdklab
2023-04-14 9:59 dpdklab
2023-04-14 10:03 dpdklab
2023-04-14 10:04 dpdklab
2023-04-14 10:04 dpdklab
2023-04-14 10:13 dpdklab
2023-04-14 10:13 dpdklab
2023-04-14 10:16 dpdklab
2023-04-14 10:23 dpdklab
2023-04-14 10:32 dpdklab
2023-04-14 10:33 dpdklab
2023-04-14 10:41 dpdklab
2023-04-14 10:50 dpdklab
2023-04-14 10:52 dpdklab
2023-04-14 10:53 dpdklab
2023-04-14 10:56 dpdklab
2023-04-14 10:58 dpdklab
2023-04-14 11:05 dpdklab
2023-04-14 11:55 dpdklab
2023-04-14 11:56 dpdklab
2023-04-14 12:28 dpdklab
2023-04-14 13:03 dpdklab
2023-04-14 13:03 dpdklab
2023-04-14 13:31 dpdklab
2023-04-14 13:32 dpdklab
2023-04-14 13:55 dpdklab
2023-04-14 22:07 dpdklab
2023-04-14 22:11 dpdklab
2023-04-14 22:17 dpdklab
2023-04-14 22:32 dpdklab
2023-04-14 22:36 dpdklab
2023-04-14 22:42 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=202304140537.33E5bJK7582469@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).