From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw127939 [PATCH] net/ice: fix outer UDP checksum offload
Date: Fri, 2 Jun 2023 09:26:09 +0800 [thread overview]
Message-ID: <202306020126.3521Q9RA1594366@localhost.localdomain> (raw)
In-Reply-To: <20230602014253.2347419-1-zhichaox.zeng@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/127939
_Compilation OK_
Submitter: Zhichao Zeng <zhichaox.zeng@intel.com>
Date: Fri, 2 Jun 2023 09:42:53 +0800
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 79314710e9603e0bd3a2521bb48be8655faced1d
127939 --> 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-06-02 1:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230602014253.2347419-1-zhichaox.zeng@intel.com>
2023-06-02 1:26 ` qemudev [this message]
2023-06-02 1:30 ` qemudev
2023-06-02 1:38 ` checkpatch
2023-06-02 15:22 ` |FAILURE| " 0-day Robot
2023-06-02 2:06 |SUCCESS| " dpdklab
2023-06-02 2:07 dpdklab
2023-06-02 2:07 dpdklab
2023-06-02 2:07 dpdklab
2023-06-02 2:08 dpdklab
2023-06-02 2:08 dpdklab
2023-06-02 2:12 dpdklab
2023-06-02 2:12 dpdklab
2023-06-02 2:24 dpdklab
2023-06-02 2:34 dpdklab
2023-06-02 2:53 dpdklab
2023-06-02 3:06 dpdklab
2023-06-02 3:17 dpdklab
2023-06-02 3:50 dpdklab
2023-06-08 22:06 dpdklab
2023-06-08 22:08 dpdklab
2023-06-08 22:08 dpdklab
2023-06-08 22:09 dpdklab
2023-06-08 22:10 dpdklab
2023-06-08 22:11 dpdklab
2023-06-08 22:11 dpdklab
2023-06-09 22:20 dpdklab
2023-06-09 22:29 dpdklab
2023-06-09 22:29 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=202306020126.3521Q9RA1594366@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).