From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw141118 [PATCH v3] net/mana: fix uninitialized scalar variable
Date: Thu, 13 Jun 2024 01:59:09 +0800 [thread overview]
Message-ID: <202406121759.45CHx9ld1487198@localhost.localdomain> (raw)
In-Reply-To: <20240612182332.804748-1-mahmoudmatook.mm@gmail.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/141118
_Compilation OK_
Submitter: Mahmoud Maatuq <mahmoudmatook.mm@gmail.com>
Date: Wed, 12 Jun 2024 22:23:31 +0400
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: b1a6f8deeee2d30b6e25d9a5c8279dfc9401d9aa
141118 --> 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:[~2024-06-12 18:27 UTC|newest]
Thread overview: 105+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240612182332.804748-1-mahmoudmatook.mm@gmail.com>
2024-06-12 17:59 ` qemudev [this message]
2024-06-12 18:03 ` qemudev
2024-06-12 18:25 ` checkpatch
2024-06-12 19:25 ` 0-day Robot
2024-06-13 0:04 ` |SUCCESS| pw141118 [PATCH] [v3] net/mana: fix uninitialized scalar v dpdklab
2024-06-13 1:06 ` dpdklab
2024-06-13 1:32 ` dpdklab
2024-06-13 1:32 ` dpdklab
2024-06-13 1:32 ` dpdklab
2024-06-13 1:32 ` dpdklab
2024-06-13 1:34 ` dpdklab
2024-06-13 1:34 ` dpdklab
2024-06-13 1:34 ` dpdklab
2024-06-13 1:34 ` dpdklab
2024-06-13 1:34 ` dpdklab
2024-06-13 1:35 ` dpdklab
2024-06-13 1:35 ` dpdklab
2024-06-13 1:35 ` dpdklab
2024-06-13 1:35 ` dpdklab
2024-06-13 1:35 ` dpdklab
2024-06-13 1:35 ` dpdklab
2024-06-13 1:36 ` dpdklab
2024-06-13 1:36 ` dpdklab
2024-06-13 1:36 ` dpdklab
2024-06-13 1:36 ` dpdklab
2024-06-13 1:36 ` dpdklab
2024-06-13 1:37 ` dpdklab
2024-06-13 1:37 ` dpdklab
2024-06-13 1:37 ` dpdklab
2024-06-13 1:37 ` dpdklab
2024-06-13 1:37 ` dpdklab
2024-06-13 1:37 ` dpdklab
2024-06-13 1:37 ` dpdklab
2024-06-13 1:37 ` dpdklab
2024-06-13 1:37 ` dpdklab
2024-06-13 1:38 ` dpdklab
2024-06-13 1:38 ` dpdklab
2024-06-13 1:38 ` dpdklab
2024-06-13 1:38 ` dpdklab
2024-06-13 1:38 ` dpdklab
2024-06-13 1:38 ` dpdklab
2024-06-13 1:38 ` dpdklab
2024-06-13 1:38 ` dpdklab
2024-06-13 1:38 ` dpdklab
2024-06-13 1:38 ` dpdklab
2024-06-13 1:39 ` dpdklab
2024-06-13 1:39 ` dpdklab
2024-06-13 1:39 ` dpdklab
2024-06-13 1:39 ` dpdklab
2024-06-13 1:39 ` dpdklab
2024-06-13 1:39 ` dpdklab
2024-06-13 1:39 ` dpdklab
2024-06-13 1:39 ` dpdklab
2024-06-13 1:40 ` dpdklab
2024-06-13 1:40 ` dpdklab
2024-06-13 1:40 ` dpdklab
2024-06-13 1:40 ` dpdklab
2024-06-13 1:40 ` dpdklab
2024-06-13 1:40 ` dpdklab
2024-06-13 1:40 ` dpdklab
2024-06-13 1:40 ` dpdklab
2024-06-13 1:41 ` dpdklab
2024-06-13 1:41 ` dpdklab
2024-06-13 1:41 ` dpdklab
2024-06-13 1:42 ` dpdklab
2024-06-13 1:42 ` dpdklab
2024-06-13 1:42 ` dpdklab
2024-06-13 1:42 ` dpdklab
2024-06-13 1:42 ` dpdklab
2024-06-13 1:42 ` dpdklab
2024-06-13 1:42 ` dpdklab
2024-06-13 1:43 ` dpdklab
2024-06-13 1:43 ` dpdklab
2024-06-13 1:43 ` dpdklab
2024-06-13 1:43 ` dpdklab
2024-06-13 1:43 ` dpdklab
2024-06-13 1:44 ` dpdklab
2024-06-13 1:44 ` dpdklab
2024-06-13 1:44 ` dpdklab
2024-06-13 1:44 ` dpdklab
2024-06-13 1:44 ` dpdklab
2024-06-13 1:44 ` dpdklab
2024-06-13 1:44 ` dpdklab
2024-06-13 1:45 ` dpdklab
2024-06-13 1:45 ` dpdklab
2024-06-13 1:45 ` dpdklab
2024-06-13 1:45 ` dpdklab
2024-06-13 1:47 ` dpdklab
2024-06-13 1:48 ` dpdklab
2024-06-13 1:49 ` dpdklab
2024-06-13 1:52 ` dpdklab
2024-06-13 1:52 ` dpdklab
2024-06-13 1:52 ` dpdklab
2024-06-13 1:53 ` dpdklab
2024-06-13 1:53 ` dpdklab
2024-06-13 1:55 ` dpdklab
2024-06-13 1:56 ` dpdklab
2024-06-13 1:56 ` dpdklab
2024-06-13 1:56 ` dpdklab
2024-06-13 1:59 ` dpdklab
2024-06-13 1:59 ` dpdklab
2024-06-13 2:02 ` dpdklab
2024-06-13 3:27 ` dpdklab
2024-06-13 4:06 ` dpdklab
2024-06-13 4:51 ` 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=202406121759.45CHx9ld1487198@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).