From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123774 [PATCH v3] net/iavf: add debug checks for mbuf
Date: Mon, 13 Feb 2023 16:24:20 +0800 [thread overview]
Message-ID: <202302130824.31D8OKfp2959662@localhost.localdomain> (raw)
In-Reply-To: <20230213083150.295194-1-mingjinx.ye@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123774
_Compilation OK_
Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Mon, 13 Feb 2023 08:31:50 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: b52ae18379821da6a920823b6966ddd0e94ebe6f
123774 --> 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-13 8:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230213083150.295194-1-mingjinx.ye@intel.com>
2023-02-13 8:24 ` qemudev [this message]
2023-02-13 8:28 ` qemudev
2023-02-13 8:35 ` checkpatch
2023-02-14 0:19 ` 0-day Robot
2023-02-13 8:59 |SUCCESS| pw123774 [PATCH] [v3] " dpdklab
2023-02-13 8:59 dpdklab
2023-02-13 9:02 dpdklab
2023-02-13 9:03 dpdklab
2023-02-13 9:04 dpdklab
2023-02-13 9:06 dpdklab
2023-02-13 9:08 dpdklab
2023-02-13 9:12 dpdklab
2023-02-13 9:16 dpdklab
2023-02-13 9:16 dpdklab
2023-02-13 9:16 dpdklab
2023-02-13 9:19 dpdklab
2023-02-13 9:22 dpdklab
2023-02-13 10:13 dpdklab
2023-02-13 15:10 dpdklab
2023-02-13 16:49 dpdklab
2023-02-13 16:51 dpdklab
2023-02-13 17:04 dpdklab
2023-02-13 17:08 dpdklab
2023-02-13 17:13 dpdklab
2023-02-13 17:14 dpdklab
2023-02-13 17:21 dpdklab
2023-02-13 17:23 dpdklab
2023-02-13 17:26 dpdklab
2023-02-13 17:32 dpdklab
2023-02-13 17:34 dpdklab
2023-02-13 17:35 dpdklab
2023-02-13 17:41 dpdklab
2023-02-13 17:42 dpdklab
2023-02-14 19:52 dpdklab
2023-02-15 10:00 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=202302130824.31D8OKfp2959662@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).