From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126202 [PATCH v3] pipeline: fix double free error for table stats
Date: Tue, 18 Apr 2023 02:57:06 +0800 [thread overview]
Message-ID: <202304171857.33HIv6Eh2580065@localhost.localdomain> (raw)
In-Reply-To: <20230417112243.727023-1-kamalakannan.r@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126202
_Compilation OK_
Submitter: Kamalakannan R <kamalakannan.r@intel.com>
Date: Mon, 17 Apr 2023 16:52:43 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 3b3fef9de22af80d173453ab65a80b01ce38cbfd
126202 --> 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-17 19:11 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230417112243.727023-1-kamalakannan.r@intel.com>
2023-04-17 18:57 ` qemudev [this message]
2023-04-17 19:00 ` |WARNING| " checkpatch
2023-04-17 19:01 ` |SUCCESS| " qemudev
2023-04-17 23:36 |SUCCESS| pw126202 [PATCH] [v3] " dpdklab
2023-04-17 23:37 dpdklab
2023-04-17 23:39 dpdklab
2023-04-17 23:43 dpdklab
2023-04-17 23:44 dpdklab
2023-04-17 23:45 dpdklab
2023-04-17 23:46 dpdklab
2023-04-17 23:51 dpdklab
2023-04-17 23:51 dpdklab
2023-04-17 23:52 dpdklab
2023-04-17 23:55 dpdklab
2023-04-18 0:00 dpdklab
2023-04-18 0:04 dpdklab
2023-04-18 0:15 dpdklab
2023-04-18 0:17 dpdklab
2023-04-18 0:23 dpdklab
2023-04-18 0:23 dpdklab
2023-04-18 0:23 dpdklab
2023-04-18 0:24 dpdklab
2023-04-18 0:25 dpdklab
2023-04-18 0:26 dpdklab
2023-04-18 0:30 dpdklab
2023-04-18 0:30 dpdklab
2023-04-18 0:34 dpdklab
2023-04-18 0:39 dpdklab
2023-04-18 0:43 dpdklab
2023-04-18 0:45 dpdklab
2023-04-18 0:52 dpdklab
2023-04-18 0:53 dpdklab
2023-04-18 1:10 dpdklab
2023-04-18 1:19 dpdklab
2023-04-18 1:20 dpdklab
2023-04-18 1:22 dpdklab
2023-04-18 1:22 dpdklab
2023-04-18 1:28 dpdklab
2023-04-18 1:29 dpdklab
2023-04-18 1:33 dpdklab
2023-04-18 1:34 dpdklab
2023-04-18 1:35 dpdklab
2023-04-18 1:49 dpdklab
2023-04-18 1:55 dpdklab
2023-04-18 1:59 dpdklab
2023-04-18 2:11 dpdklab
2023-04-18 2:12 dpdklab
2023-04-18 2:18 dpdklab
2023-04-18 2:21 dpdklab
2023-04-18 2:22 dpdklab
2023-04-18 2:26 dpdklab
2023-04-18 2:26 dpdklab
2023-04-18 6:05 dpdklab
2023-04-18 6:22 dpdklab
2023-04-18 6:31 dpdklab
2023-04-18 6:51 dpdklab
2023-04-18 11:07 dpdklab
2023-04-18 11:08 dpdklab
2023-04-18 12:13 dpdklab
2023-04-18 12:14 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=202304171857.33HIv6Eh2580065@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).