From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125035 [PATCH] mldev: fix identical code in conditional branches
Date: Sat, 11 Mar 2023 22:53:46 +0800 [thread overview]
Message-ID: <202303111453.32BErk043960122@localhost.localdomain> (raw)
In-Reply-To: <20230311145606.5523-1-syalavarthi@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125035
_Compilation OK_
Submitter: Srikanth Yalavarthi <syalavarthi@marvell.com>
Date: Sat, 11 Mar 2023 06:56:06 -0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 0fd1386c30c3ad9365d7fdd2829bf7cb2e1b9dff
125035 --> 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-11 15:07 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230311145606.5523-1-syalavarthi@marvell.com>
2023-03-11 14:53 ` qemudev [this message]
2023-03-11 14:57 ` checkpatch
2023-03-11 14:57 ` qemudev
2023-03-11 17:19 ` 0-day Robot
2023-03-11 19:46 dpdklab
2023-03-11 19:47 dpdklab
2023-03-11 19:50 dpdklab
2023-03-11 19:57 dpdklab
2023-03-11 19:57 dpdklab
2023-03-11 19:58 dpdklab
2023-03-11 20:01 dpdklab
2023-03-11 20:04 dpdklab
2023-03-11 20:04 dpdklab
2023-03-11 20:06 dpdklab
2023-03-11 20:11 dpdklab
2023-03-11 20:16 dpdklab
2023-03-11 20:21 dpdklab
2023-03-11 20:24 dpdklab
2023-03-11 20:28 dpdklab
2023-03-11 20:31 dpdklab
2023-03-11 20:32 dpdklab
2023-03-11 20:34 dpdklab
2023-03-11 20:34 dpdklab
2023-03-11 20:38 dpdklab
2023-03-11 20:40 dpdklab
2023-03-11 20:42 dpdklab
2023-03-11 20:43 dpdklab
2023-03-11 20:44 dpdklab
2023-03-11 20:45 dpdklab
2023-03-11 20:49 dpdklab
2023-03-11 20:57 dpdklab
2023-03-11 21:33 dpdklab
2023-03-12 15:20 dpdklab
2023-03-12 15:52 dpdklab
2023-03-12 16:59 dpdklab
2023-03-12 17:04 dpdklab
2023-03-13 2:35 dpdklab
2023-03-13 2:37 dpdklab
2023-03-13 2:38 dpdklab
2023-03-13 2:41 dpdklab
2023-03-13 2:44 dpdklab
2023-03-13 2:46 dpdklab
2023-03-13 2:47 dpdklab
2023-03-13 2:50 dpdklab
2023-03-13 2:53 dpdklab
2023-03-13 2:55 dpdklab
2023-03-13 2:56 dpdklab
2023-03-13 2:59 dpdklab
2023-03-13 3:39 dpdklab
2023-03-13 3:39 dpdklab
2023-03-13 3:47 dpdklab
2023-03-13 3:51 dpdklab
2023-03-13 4:04 dpdklab
2023-03-13 4:08 dpdklab
2023-03-13 4:09 dpdklab
2023-03-13 4:15 dpdklab
2023-03-13 4:19 dpdklab
2023-03-13 4:19 dpdklab
2023-03-13 4:21 dpdklab
2023-03-13 4:23 dpdklab
2023-03-13 4:55 dpdklab
2023-03-13 4:55 dpdklab
2023-03-13 19:41 dpdklab
2023-03-13 21:04 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=202303111453.32BErk043960122@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).