From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw156383-156386 [PATCH v2 4/4] net/iavf: remove duplicate in scalar offload list
Date: Tue, 2 Sep 2025 18:19:52 +0800 [thread overview]
Message-ID: <202509021019.582AJqWw624366@localhost.localdomain> (raw)
In-Reply-To: <20250902104859.2100141-5-ciara.loftus@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/156386
_Compilation OK_
Submitter: Ciara Loftus <ciara.loftus@intel.com>
Date: Tue, 2 Sep 2025 10:48:56 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 052ae311091c808269adcf57c7aef90fcea23f26
156383-156386 --> 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:[~2025-09-02 10:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250902104859.2100141-5-ciara.loftus@intel.com>
2025-09-02 10:19 ` qemudev [this message]
2025-09-02 10:24 ` qemudev
2025-09-02 10:48 ` |SUCCESS| pw156386 " checkpatch
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=202509021019.582AJqWw624366@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).