From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124142 [PATCH] net/gve: fix Rx no mbufs stats counter update
Date: Sun, 19 Feb 2023 08:27:59 +0800 [thread overview]
Message-ID: <202302190027.31J0RxPa2836176@localhost.localdomain> (raw)
In-Reply-To: <20230219003059.85479-1-levendsayar@gmail.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124142
_Compilation OK_
Submitter: Levend Sayar <levendsayar@gmail.com>
Date: Sun, 19 Feb 2023 03:30:59 +0300
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: a5d34ecbb4b017e1b6c20a1f28127ffeaa1237af
124142 --> 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-02-19 0:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230219003059.85479-1-levendsayar@gmail.com>
2023-02-19 0:27 ` qemudev [this message]
2023-02-19 0:31 ` checkpatch
2023-02-19 0:32 ` qemudev
2023-02-19 3:19 ` 0-day Robot
2023-02-19 1:21 dpdklab
2023-02-19 1:22 dpdklab
2023-02-19 1:23 dpdklab
2023-02-19 1:27 dpdklab
2023-02-19 1:31 dpdklab
2023-02-19 1:33 dpdklab
2023-02-19 1:34 dpdklab
2023-02-19 1:39 dpdklab
2023-02-19 1:40 dpdklab
2023-02-19 1:47 dpdklab
2023-02-19 2:15 dpdklab
2023-02-19 2:29 dpdklab
2023-02-19 2:29 dpdklab
2023-02-19 2:36 dpdklab
2023-02-19 2:41 dpdklab
2023-02-19 2:47 dpdklab
2023-02-19 2:48 dpdklab
2023-02-19 2:49 dpdklab
2023-02-19 2:50 dpdklab
2023-02-19 2:51 dpdklab
2023-02-19 2:55 dpdklab
2023-02-19 2:56 dpdklab
2023-02-19 2:58 dpdklab
2023-02-19 2:58 dpdklab
2023-02-19 3:35 dpdklab
2023-02-20 5:44 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=202302190027.31J0RxPa2836176@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).