From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw128290-128323 [PATCH v4 34/34] net/sfc: use conntrack assistance counters in transfer flows
Date: Wed, 7 Jun 2023 20:57:26 +0800 [thread overview]
Message-ID: <202306071257.357CvQnM1053504@localhost.localdomain> (raw)
In-Reply-To: <20230607130245.8048-35-ivan.malov@arknetworks.am>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/128323
_Compilation OK_
Submitter: Ivan Malov <ivan.malov@arknetworks.am>
Date: Wed, 7 Jun 2023 17:02:12 +0400
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 05a00c75c6277a19aaeba2058d2ff95cccd73584
128290-128323 --> 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-06-07 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230607130245.8048-35-ivan.malov@arknetworks.am>
2023-06-07 12:57 ` qemudev [this message]
2023-06-07 13:01 ` qemudev
2023-06-07 13:08 ` |SUCCESS| pw128323 " checkpatch
2023-06-07 14:19 ` 0-day Robot
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=202306071257.357CvQnM1053504@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).