From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw129157 [PATCH v2] net/idpf: fix error path processing
Date: Fri, 30 Jun 2023 18:31:24 +0800 [thread overview]
Message-ID: <202306301031.35UAVOrH1586637@localhost.localdomain> (raw)
In-Reply-To: <20230630185402.13307-1-mingxia.liu@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/129157
_Compilation OK_
Submitter: Mingxia Liu <mingxia.liu@intel.com>
Date: Fri, 30 Jun 2023 18:54:02 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 95d1323996755d6b4be92b211362d30b5072ac55
129157 --> 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-30 10:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230630185402.13307-1-mingxia.liu@intel.com>
2023-06-30 10:31 ` qemudev [this message]
2023-06-30 10:35 ` qemudev
2023-06-30 10:36 ` checkpatch
2023-06-30 11:39 ` 0-day Robot
2023-06-30 22:35 |SUCCESS| pw129157 [PATCH] [v2] " dpdklab
2023-06-30 22:35 dpdklab
2023-06-30 22:43 dpdklab
2023-06-30 22:44 dpdklab
2023-06-30 22:44 dpdklab
2023-06-30 22:44 dpdklab
2023-06-30 22:44 dpdklab
2023-06-30 22:54 dpdklab
2023-06-30 23:38 dpdklab
2023-06-30 23:39 dpdklab
2023-06-30 23:45 dpdklab
2023-06-30 23:51 dpdklab
2023-06-30 23:56 dpdklab
2023-06-30 23:56 dpdklab
2023-06-30 23:56 dpdklab
2023-06-30 23:56 dpdklab
2023-07-01 0:05 dpdklab
2023-07-01 0:06 dpdklab
2023-07-01 0:06 dpdklab
2023-07-01 0:10 dpdklab
2023-07-01 0:13 dpdklab
2023-07-01 0:14 dpdklab
2023-07-01 3:19 dpdklab
2023-07-01 3:20 dpdklab
2023-07-01 3:31 dpdklab
2023-07-01 7:24 dpdklab
2023-07-01 7:56 dpdklab
2023-07-01 8:42 dpdklab
2023-07-01 8:43 dpdklab
2023-07-01 8:44 dpdklab
2023-07-02 13:44 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=202306301031.35UAVOrH1586637@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).