automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124593 [PATCH v1] eventdev: fix invalid memory free operation
Date: Wed, 1 Mar 2023 16:09:35 +0800	[thread overview]
Message-ID: <202303010809.32189ZdM951435@localhost.localdomain> (raw)
In-Reply-To: <20230228213123.371897-1-abdullah.sevincer@intel.com>

Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124593

_Compilation OK_

Submitter: Abdullah Sevincer <abdullah.sevincer@intel.com>
Date: Tue, 28 Feb 2023 15:31:23 -0600
DPDK git baseline: Repo:dpdk-next-eventdev
  Branch: for-main
  CommitID: ca88db3ae76d878a8febe3fe1effe0b677403845

124593 --> 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


  parent reply	other threads:[~2023-03-01  8:23 UTC|newest]

Thread overview: 161+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230228213123.371897-1-abdullah.sevincer@intel.com>
2023-02-28 21:31 ` checkpatch
2023-02-28 23:43 ` 0-day Robot
2023-03-01  8:09 ` qemudev [this message]
2023-03-01  8:10 ` qemudev
2023-03-01 22:41 |SUCCESS| pw124593 [PATCH] [v1] " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-03-01 22:40 dpdklab
2023-03-01 21:19 dpdklab
2023-03-01 21:18 dpdklab
2023-03-01 21:18 dpdklab
2023-03-01 21:17 dpdklab
2023-03-01 21:15 dpdklab
2023-03-01 21:09 dpdklab
2023-03-01 21:09 dpdklab
2023-03-01 21:07 dpdklab
2023-03-01 21:02 dpdklab
2023-03-01 21:01 dpdklab
2023-03-01 20:50 dpdklab
2023-03-01 20:43 dpdklab
2023-03-01 20:37 dpdklab
2023-03-01 19:51 dpdklab
2023-03-01 19:50 dpdklab
2023-03-01 19:21 dpdklab
2023-03-01 19:20 dpdklab
2023-03-01 19:18 dpdklab
2023-03-01 19:15 dpdklab
2023-03-01 19:13 dpdklab
2023-03-01 19:11 dpdklab
2023-03-01 19:06 dpdklab
2023-03-01 19:03 dpdklab
2023-03-01 19:00 dpdklab
2023-03-01 18:51 dpdklab
2023-03-01 18:51 dpdklab
2023-03-01 18:51 dpdklab
2023-03-01 18:49 dpdklab
2023-03-01 18:34 dpdklab
2023-03-01 18:27 dpdklab
2023-03-01 18:27 dpdklab
2023-03-01 18:25 dpdklab
2023-03-01 18:20 dpdklab
2023-03-01 18:14 dpdklab
2023-03-01 18:10 dpdklab
2023-03-01 18:09 dpdklab
2023-03-01 18:06 dpdklab
2023-03-01 18:05 dpdklab
2023-03-01 18:04 dpdklab
2023-03-01 18:00 dpdklab
2023-03-01 17:57 dpdklab
2023-03-01 17:57 dpdklab
2023-03-01 17:56 dpdklab
2023-03-01 17:20 dpdklab
2023-03-01 17:18 dpdklab
2023-03-01 17:17 dpdklab
2023-03-01 17:11 dpdklab
2023-03-01 17:11 dpdklab
2023-03-01 17:09 dpdklab
2023-03-01 17:08 dpdklab
2023-03-01 17:06 dpdklab
2023-03-01 17:06 dpdklab
2023-03-01 16:57 dpdklab
2023-03-01 16:49 dpdklab
2023-03-01 16:45 dpdklab
2023-03-01 16:45 dpdklab
2023-03-01 16:38 dpdklab
2023-03-01 16:37 dpdklab
2023-03-01 16:33 dpdklab
2023-03-01 16:30 dpdklab
2023-03-01 16:29 dpdklab
2023-03-01 16:28 dpdklab
2023-03-01 16:26 dpdklab
2023-03-01 16:25 dpdklab
2023-03-01 16:18 dpdklab
2023-03-01 16:15 dpdklab
2023-03-01 16:05 dpdklab
2023-03-01 15:53 dpdklab
2023-03-01 15:47 dpdklab
2023-03-01 10:31 dpdklab
2023-03-01 10:19 dpdklab
2023-03-01 10:07 dpdklab
2023-03-01  9:43 dpdklab
2023-03-01  9:23 dpdklab
2023-03-01  9:17 dpdklab
2023-03-01  9:15 dpdklab
2023-03-01  8:41 dpdklab
2023-03-01  8:34 dpdklab
2023-03-01  8:29 dpdklab
2023-03-01  8:16 dpdklab
2023-03-01  8:16 dpdklab
2023-03-01  8:05 dpdklab
2023-03-01  7:56 dpdklab
2023-03-01  7:44 dpdklab
2023-03-01  7:41 dpdklab
2023-03-01  7:24 dpdklab
2023-03-01  7:11 dpdklab
2023-03-01  7:06 dpdklab
2023-03-01  6:53 dpdklab
2023-03-01  6:51 dpdklab
2023-03-01  6:39 dpdklab
2023-03-01  6:37 dpdklab
2023-03-01  6:24 dpdklab
2023-03-01  6:19 dpdklab
2023-03-01  6:08 dpdklab
2023-03-01  5:59 dpdklab
2023-03-01  5:56 dpdklab
2023-03-01  5:46 dpdklab
2023-03-01  5:39 dpdklab
2023-03-01  5:34 dpdklab
2023-03-01  5:27 dpdklab
2023-03-01  5:11 dpdklab
2023-03-01  4:54 dpdklab
2023-03-01  4:41 dpdklab
2023-03-01  4:29 dpdklab
2023-03-01  4:00 dpdklab
2023-03-01  3:47 dpdklab
2023-03-01  3:39 dpdklab
2023-03-01  3:32 dpdklab
2023-03-01  3:27 dpdklab
2023-03-01  3:27 dpdklab
2023-03-01  3:24 dpdklab
2023-03-01  3:19 dpdklab
2023-03-01  3:12 dpdklab
2023-03-01  3:08 dpdklab
2023-03-01  3:07 dpdklab
2023-03-01  3:06 dpdklab
2023-03-01  2:57 dpdklab
2023-03-01  2:54 dpdklab
2023-03-01  2:45 dpdklab
2023-03-01  2:43 dpdklab
2023-03-01  2:39 dpdklab
2023-03-01  2:37 dpdklab
2023-03-01  2:35 dpdklab
2023-03-01  2:31 dpdklab
2023-03-01  2:29 dpdklab
2023-03-01  2:27 dpdklab
2023-03-01  2:17 dpdklab
2023-03-01  2:16 dpdklab
2023-03-01  2:12 dpdklab
2023-03-01  2:09 dpdklab
2023-03-01  2:08 dpdklab
2023-03-01  1:58 dpdklab
2023-03-01  1:46 dpdklab
2023-03-01  1:44 dpdklab
2023-03-01  1:42 dpdklab
2023-03-01  1:40 dpdklab
2023-03-01  1:32 dpdklab
2023-03-01  1:19 dpdklab
2023-03-01  1:15 dpdklab
2023-03-01  1:06 dpdklab
2023-03-01  0:52 dpdklab
2023-03-01  0:47 dpdklab
2023-03-01  0:47 dpdklab
2023-03-01  0:38 dpdklab
2023-03-01  0:25 dpdklab
2023-03-01  0:11 dpdklab
2023-02-28 23:49 dpdklab
2023-02-28 23:42 dpdklab
2023-02-28 23:40 dpdklab
2023-02-28 23:33 dpdklab
2023-02-28 23:31 dpdklab
2023-02-28 23:24 dpdklab
2023-02-28 23:21 dpdklab
2023-02-28 23:15 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=202303010809.32189ZdM951435@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).