From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121457 [PATCH v4] net/iavf: add lock for vf commands
Date: Thu, 29 Dec 2022 06:52:22 +0800 [thread overview]
Message-ID: <202212282252.2BSMqM27938809@localhost.localdomain> (raw)
In-Reply-To: <20221228230025.1430743-1-mkp@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/121457
_Compilation OK_
Submitter: Mike Pattrick <mkp@redhat.com>
Date: Wed, 28 Dec 2022 18:00:25 -0500
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 43d326b6f923f32473f550228910e1bd5de3f3fb
121457 --> 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:[~2022-12-28 23:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221228230025.1430743-1-mkp@redhat.com>
2022-12-28 22:52 ` qemudev [this message]
2022-12-28 22:56 ` qemudev
2022-12-28 23:01 ` checkpatch
2022-12-28 23:59 ` 0-day Robot
2022-12-29 1:18 |SUCCESS| pw121457 [PATCH] [v4] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2022-12-29 1:07 dpdklab
2022-12-29 1:07 dpdklab
2022-12-29 1:05 dpdklab
2022-12-29 0:56 dpdklab
2022-12-29 0:55 dpdklab
2022-12-29 0:53 dpdklab
2022-12-29 0:52 dpdklab
2022-12-29 0:51 dpdklab
2022-12-29 0:49 dpdklab
2022-12-29 0:44 dpdklab
2022-12-29 0:38 dpdklab
2022-12-29 0:29 dpdklab
2022-12-29 0:28 dpdklab
2022-12-29 0:28 dpdklab
2022-12-29 0:07 dpdklab
2022-12-28 23:49 dpdklab
2022-12-28 23:45 dpdklab
2022-12-28 23:38 dpdklab
2022-12-28 23:34 dpdklab
2022-12-28 23:31 dpdklab
2022-12-28 23:29 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=202212282252.2BSMqM27938809@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).