From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw127155 [PATCH] net/ice: fix data length check
Date: Tue, 23 May 2023 19:24:00 +0800 [thread overview]
Message-ID: <202305231124.34NBO0FL2018196@localhost.localdomain> (raw)
In-Reply-To: <20230522181447.2747713-1-qi.z.zhang@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/127155
_Compilation OK_
Submitter: Qi Zhang <qi.z.zhang@intel.com>
Date: Mon, 22 May 2023 14:14:47 -0400
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 484c460730e3d85382d089ef1aeaffd28048de49
127155 --> 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 prev parent reply other threads:[~2023-05-23 11:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230522181447.2747713-1-qi.z.zhang@intel.com>
2023-05-22 9:56 ` checkpatch
2023-05-22 15:19 ` |FAILURE| " 0-day Robot
2023-05-23 11:24 ` qemudev [this message]
2023-05-23 11:24 ` |SUCCESS| " qemudev
2023-05-22 11:21 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-05-22 11:15 dpdklab
2023-05-22 11:10 dpdklab
2023-05-22 11:10 dpdklab
2023-05-22 11:04 dpdklab
2023-05-22 11:04 dpdklab
2023-05-22 10:59 dpdklab
2023-05-22 10:58 dpdklab
2023-05-22 10:57 dpdklab
2023-05-22 10:55 dpdklab
2023-05-22 10:52 dpdklab
2023-05-22 10:50 dpdklab
2023-05-22 10:46 dpdklab
2023-05-22 10:43 dpdklab
2023-05-22 10:38 dpdklab
2023-05-22 10:32 dpdklab
2023-05-22 10:32 dpdklab
2023-05-22 10:31 dpdklab
2023-05-22 10:31 dpdklab
2023-05-22 10:30 dpdklab
2023-05-22 10:30 dpdklab
2023-05-22 10:24 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=202305231124.34NBO0FL2018196@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).