From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126072 [PATCH] bitmap: add scan init at given position
Date: Fri, 14 Apr 2023 16:32:10 +0800 [thread overview]
Message-ID: <202304140832.33E8WAq2799743@localhost.localdomain> (raw)
In-Reply-To: <20230414083943.270651-1-vfialko@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126072
_Compilation OK_
Submitter: Volodymyr Fialko <vfialko@marvell.com>
Date: Fri, 14 Apr 2023 10:39:43 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 3b3fef9de22af80d173453ab65a80b01ce38cbfd
126072 --> 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-04-14 8:46 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230414083943.270651-1-vfialko@marvell.com>
2023-04-14 8:32 ` qemudev [this message]
2023-04-14 8:36 ` qemudev
2023-04-14 8:40 ` checkpatch
2023-04-14 9:59 ` 0-day Robot
2023-04-14 22:41 dpdklab
2023-04-14 22:45 dpdklab
2023-04-14 22:45 dpdklab
2023-04-14 22:46 dpdklab
2023-04-14 22:52 dpdklab
2023-04-14 22:53 dpdklab
2023-04-14 22:58 dpdklab
2023-04-14 22:58 dpdklab
2023-04-14 23:10 dpdklab
2023-04-14 23:18 dpdklab
2023-04-14 23:38 dpdklab
2023-04-14 23:40 dpdklab
2023-04-14 23:43 dpdklab
2023-04-14 23:44 dpdklab
2023-04-14 23:47 dpdklab
2023-04-14 23:48 dpdklab
2023-04-14 23:52 dpdklab
2023-04-14 23:52 dpdklab
2023-04-15 0:01 dpdklab
2023-04-15 0:04 dpdklab
2023-04-15 0:13 dpdklab
2023-04-15 0:14 dpdklab
2023-04-15 0:29 dpdklab
2023-04-15 0:33 dpdklab
2023-04-15 0:33 dpdklab
2023-04-15 0:34 dpdklab
2023-04-15 0:35 dpdklab
2023-04-15 0:37 dpdklab
2023-04-15 0:41 dpdklab
2023-04-15 0:48 dpdklab
2023-04-15 0:49 dpdklab
2023-04-15 0:52 dpdklab
2023-04-15 0:55 dpdklab
2023-04-15 1:00 dpdklab
2023-04-15 1:02 dpdklab
2023-04-15 1:04 dpdklab
2023-04-15 1:10 dpdklab
2023-04-15 1:12 dpdklab
2023-04-15 1:13 dpdklab
2023-04-15 1:17 dpdklab
2023-04-15 1:18 dpdklab
2023-04-15 1:18 dpdklab
2023-04-15 1:23 dpdklab
2023-04-15 1:23 dpdklab
2023-04-15 1:41 dpdklab
2023-04-15 6:28 dpdklab
2023-04-15 6:32 dpdklab
2023-04-15 6:37 dpdklab
2023-04-15 6:52 dpdklab
2023-04-15 6:56 dpdklab
2023-04-15 6:57 dpdklab
2023-04-15 7:02 dpdklab
2023-04-15 7:46 dpdklab
2023-04-15 8:21 dpdklab
2023-04-15 8:31 dpdklab
2023-04-15 11:17 dpdklab
2023-04-15 11:17 dpdklab
2023-04-15 11:46 dpdklab
2023-04-15 11:46 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=202304140832.33E8WAq2799743@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).