From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125036 [PATCH] mldev: remove variable self assignment in dev init
Date: Sat, 11 Mar 2023 22:47:50 +0800 [thread overview]
Message-ID: <202303111447.32BElotS3907643@localhost.localdomain> (raw)
In-Reply-To: <20230311145705.9178-1-syalavarthi@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125036
_Compilation OK_
Submitter: Srikanth Yalavarthi <syalavarthi@marvell.com>
Date: Sat, 11 Mar 2023 06:57:04 -0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 0fd1386c30c3ad9365d7fdd2829bf7cb2e1b9dff
125036 --> 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:01 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230311145705.9178-1-syalavarthi@marvell.com>
2023-03-11 14:47 ` qemudev [this message]
2023-03-11 14:51 ` qemudev
2023-03-11 14:58 ` checkpatch
2023-03-11 17:39 ` 0-day Robot
2023-03-11 16:14 dpdklab
2023-03-11 16:16 dpdklab
2023-03-11 16:19 dpdklab
2023-03-11 16:19 dpdklab
2023-03-11 16:26 dpdklab
2023-03-11 16:28 dpdklab
2023-03-11 16:30 dpdklab
2023-03-11 16:31 dpdklab
2023-03-11 16:32 dpdklab
2023-03-11 16:32 dpdklab
2023-03-11 16:35 dpdklab
2023-03-11 16:40 dpdklab
2023-03-11 16:45 dpdklab
2023-03-11 16:46 dpdklab
2023-03-11 16:47 dpdklab
2023-03-11 16:52 dpdklab
2023-03-11 16:54 dpdklab
2023-03-11 16:56 dpdklab
2023-03-11 16:56 dpdklab
2023-03-11 16:59 dpdklab
2023-03-11 17:02 dpdklab
2023-03-11 17:05 dpdklab
2023-03-11 17:06 dpdklab
2023-03-11 17:06 dpdklab
2023-03-11 17:11 dpdklab
2023-03-11 17:17 dpdklab
2023-03-11 17:31 dpdklab
2023-03-11 17:52 dpdklab
2023-03-12 11:10 dpdklab
2023-03-12 11:16 dpdklab
2023-03-12 11:22 dpdklab
2023-03-12 12:00 dpdklab
2023-03-12 20:25 dpdklab
2023-03-12 20:50 dpdklab
2023-03-12 20:56 dpdklab
2023-03-12 20:57 dpdklab
2023-03-12 20:59 dpdklab
2023-03-12 21:00 dpdklab
2023-03-12 21:04 dpdklab
2023-03-12 21:06 dpdklab
2023-03-12 21:19 dpdklab
2023-03-12 21:20 dpdklab
2023-03-12 21:25 dpdklab
2023-03-12 21:27 dpdklab
2023-03-12 21:41 dpdklab
2023-03-12 21:57 dpdklab
2023-03-12 21:58 dpdklab
2023-03-12 22:06 dpdklab
2023-03-12 22:06 dpdklab
2023-03-12 22:08 dpdklab
2023-03-12 22:13 dpdklab
2023-03-12 22:14 dpdklab
2023-03-12 22:16 dpdklab
2023-03-12 22:20 dpdklab
2023-03-12 22:22 dpdklab
2023-03-12 22:24 dpdklab
2023-03-12 22:31 dpdklab
2023-03-12 22:33 dpdklab
2023-03-12 23:21 dpdklab
2023-03-12 23:22 dpdklab
2023-03-13 14:03 dpdklab
2023-03-13 15:30 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=202303111447.32BElotS3907643@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).