From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125713 [PATCH] app/testpmd: fix GTP L2 len in checksum engine
Date: Sun, 2 Apr 2023 20:17:10 +0800 [thread overview]
Message-ID: <202304021217.332CHAJx2219568@localhost.localdomain> (raw)
In-Reply-To: <20230402122619.10078-1-rasland@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125713
_Compilation OK_
Submitter: Raslan Darawsheh <rasland@nvidia.com>
Date: Sun, 2 Apr 2023 15:26:19 +0300
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 189c02f5ec891ed02927062e124e8ca03adf74e7
125713 --> 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-02 12:31 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230402122619.10078-1-rasland@nvidia.com>
2023-04-02 12:17 ` qemudev [this message]
2023-04-02 12:21 ` qemudev
2023-04-02 12:28 ` checkpatch
2023-04-02 13:38 ` 0-day Robot
2023-04-02 12:49 dpdklab
2023-04-02 12:51 dpdklab
2023-04-02 12:52 dpdklab
2023-04-02 12:54 dpdklab
2023-04-02 12:56 dpdklab
2023-04-02 12:57 dpdklab
2023-04-02 12:57 dpdklab
2023-04-02 12:59 dpdklab
2023-04-02 12:59 dpdklab
2023-04-02 13:00 dpdklab
2023-04-02 13:04 dpdklab
2023-04-02 13:09 dpdklab
2023-04-02 13:10 dpdklab
2023-04-02 13:13 dpdklab
2023-04-02 13:13 dpdklab
2023-04-02 13:16 dpdklab
2023-04-02 13:22 dpdklab
2023-04-02 13:24 dpdklab
2023-04-02 13:25 dpdklab
2023-04-06 7:38 dpdklab
2023-04-06 7:42 dpdklab
2023-04-06 7:53 dpdklab
2023-04-06 7:57 dpdklab
2023-04-06 7:59 dpdklab
2023-04-06 8:01 dpdklab
2023-04-06 8:12 dpdklab
2023-04-06 8:20 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=202304021217.332CHAJx2219568@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).