From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126357-126362 [PATCH v2 7/7] net/idpf: register timestamp mbuf when starting dev
Date: Fri, 21 Apr 2023 15:12:19 +0800 [thread overview]
Message-ID: <202304210712.33L7CJIL3729048@localhost.localdomain> (raw)
In-Reply-To: <20230421071603.55680-8-wenjing.qiao@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126362
_Compilation OK_
Submitter: Wenjing Qiao <wenjing.qiao@intel.com>
Date: Fri, 21 Apr 2023 03:15:57 -0400
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: f649fd010f2dd3a97e15f2ef106440a79f6c95fb
126357-126362 --> 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-04-21 7:26 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230421071603.55680-8-wenjing.qiao@intel.com>
2023-04-21 7:12 ` qemudev [this message]
2023-04-21 7:16 ` qemudev
2023-04-21 7:23 ` |SUCCESS| pw126362 " checkpatch
2023-04-21 8:19 ` 0-day Robot
2023-04-22 1:28 |SUCCESS| pw126357-126362 [PATCH] [v2, " dpdklab
2023-04-22 1:29 dpdklab
2023-04-22 1:30 dpdklab
2023-04-22 1:35 dpdklab
2023-04-22 1:37 dpdklab
2023-04-22 1:37 dpdklab
2023-04-22 1:38 dpdklab
2023-04-22 1:41 dpdklab
2023-04-22 1:42 dpdklab
2023-04-22 1:44 dpdklab
2023-04-22 1:46 dpdklab
2023-04-22 1:51 dpdklab
2023-04-22 1:57 dpdklab
2023-04-22 2:22 dpdklab
2023-04-22 2:38 dpdklab
2023-04-22 2:40 dpdklab
2023-04-22 2:41 dpdklab
2023-04-22 2:57 dpdklab
2023-04-22 2:58 dpdklab
2023-04-22 3:07 dpdklab
2023-04-22 3:08 dpdklab
2023-04-22 3:08 dpdklab
2023-04-22 3:19 dpdklab
2023-04-22 3:25 dpdklab
2023-04-22 3:25 dpdklab
2023-04-22 4:13 dpdklab
2023-04-22 4:53 dpdklab
2023-04-22 6:17 dpdklab
2023-04-22 6:18 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=202304210712.33L7CJIL3729048@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).