From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw144122 [PATCH v1] common/iavf: update README documentation
Date: Tue, 17 Sep 2024 20:17:26 +0800 [thread overview]
Message-ID: <202409171217.48HCHQ5H2199135@localhost.localdomain> (raw)
In-Reply-To: <20240917114529.512696-1-soumyadeep.hore@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/144122
_Compilation OK_
Submitter: Soumyadeep Hore <soumyadeep.hore@intel.com>
Date: Tue, 17 Sep 2024 11:45:02 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 7d982a76c715e9a33e778723305272b2fe0210ec
144122 --> 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-09-17 12:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240917114529.512696-1-soumyadeep.hore@intel.com>
2024-09-17 12:17 ` qemudev [this message]
2024-09-17 12:21 ` qemudev
2024-09-17 12:44 ` checkpatch
2024-09-17 13:44 ` 0-day Robot
2024-09-17 21:07 ` |SUCCESS| pw144122 [PATCH] [v1] common/iavf: update README documenta dpdklab
2024-09-17 22:22 ` dpdklab
2024-09-17 22:23 ` dpdklab
2024-09-17 22:47 ` dpdklab
2024-09-17 22:58 ` dpdklab
2024-09-18 0:19 ` |PENDING| " dpdklab
2024-09-18 0:49 ` dpdklab
2024-09-18 1:02 ` dpdklab
2024-09-18 1:31 ` dpdklab
2024-09-18 1:37 ` |SUCCESS| " dpdklab
2024-09-18 1:47 ` dpdklab
2024-09-18 2:02 ` dpdklab
2024-09-18 3:13 ` dpdklab
2024-09-18 3:20 ` dpdklab
2024-09-18 4:47 ` dpdklab
2024-09-18 8:01 ` dpdklab
2024-09-18 9:54 ` dpdklab
2024-09-22 8:49 ` dpdklab
2024-09-22 9:02 ` 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=202409171217.48HCHQ5H2199135@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).