From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124874-124876 [PATCH v1 2/2] test/bbdev: fix unchecked ret value issue
Date: Thu, 9 Mar 2023 11:24:59 +0800 [thread overview]
Message-ID: <202303090324.3293Oxtc1541382@localhost.localdomain> (raw)
In-Reply-To: <20230309033624.61660-3-hernan.vargas@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124876
_Compilation OK_
Submitter: Hernan Vargas <hernan.vargas@intel.com>
Date: Wed, 8 Mar 2023 19:36:23 -0800
DPDK git baseline: Repo:dpdk-next-baseband
Branch: for-main
CommitID: 96d7643689efad2b2846976652a93062a505f93c
124874-124876 --> 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-03-09 3:38 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230309033624.61660-3-hernan.vargas@intel.com>
2023-03-09 3:24 ` qemudev [this message]
2023-03-09 3:28 ` qemudev
2023-03-09 3:36 ` |SUCCESS| pw124876 " checkpatch
2023-03-09 5:59 ` 0-day Robot
2023-03-11 6:38 |SUCCESS| pw124874-124876 [PATCH] [v1, " dpdklab
2023-03-11 6:43 dpdklab
2023-03-11 6:48 dpdklab
2023-03-11 6:49 dpdklab
2023-03-11 6:49 dpdklab
2023-03-11 6:49 dpdklab
2023-03-11 6:51 dpdklab
2023-03-11 6:54 dpdklab
2023-03-11 6:56 dpdklab
2023-03-11 6:59 dpdklab
2023-03-11 6:59 dpdklab
2023-03-11 7:04 dpdklab
2023-03-11 7:08 dpdklab
2023-03-11 8:01 dpdklab
2023-03-11 8:08 dpdklab
2023-03-11 8:11 dpdklab
2023-03-11 8:11 dpdklab
2023-03-11 8:12 dpdklab
2023-03-11 8:14 dpdklab
2023-03-11 8:19 dpdklab
2023-03-11 8:20 dpdklab
2023-03-11 8:20 dpdklab
2023-03-11 8:20 dpdklab
2023-03-11 8:21 dpdklab
2023-03-11 8:24 dpdklab
2023-03-11 8:28 dpdklab
2023-03-11 8:32 dpdklab
2023-03-11 9:18 dpdklab
2023-03-12 6:57 dpdklab
2023-03-12 7:24 dpdklab
2023-03-12 7:52 dpdklab
2023-03-12 8:23 dpdklab
2023-03-12 16:29 dpdklab
2023-03-12 16:45 dpdklab
2023-03-12 16:48 dpdklab
2023-03-12 16:50 dpdklab
2023-03-12 16:57 dpdklab
2023-03-12 17:02 dpdklab
2023-03-12 17:14 dpdklab
2023-03-12 17:16 dpdklab
2023-03-12 17:17 dpdklab
2023-03-12 17:19 dpdklab
2023-03-12 17:23 dpdklab
2023-03-12 17:26 dpdklab
2023-03-12 17:39 dpdklab
2023-03-12 17:40 dpdklab
2023-03-12 17:44 dpdklab
2023-03-12 17:46 dpdklab
2023-03-12 17:49 dpdklab
2023-03-12 17:51 dpdklab
2023-03-12 17:55 dpdklab
2023-03-12 17:57 dpdklab
2023-03-12 17:58 dpdklab
2023-03-12 18:00 dpdklab
2023-03-12 18:08 dpdklab
2023-03-12 18:10 dpdklab
2023-03-12 18:12 dpdklab
2023-03-12 18:13 dpdklab
2023-03-12 18:43 dpdklab
2023-03-12 18:43 dpdklab
2023-03-13 7:53 dpdklab
2023-03-13 9:47 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=202303090324.3293Oxtc1541382@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).