From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124138-124140 [PATCH v2 3/3] net/ark: resize data field to match fpga access
Date: Sat, 18 Feb 2023 05:48:09 +0800 [thread overview]
Message-ID: <202302172148.31HLm9cB2634674@localhost.localdomain> (raw)
In-Reply-To: <20230217215923.2561685-3-ed.czeck@atomicrules.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124140
_Compilation OK_
Submitter: Ed Czeck <ed.czeck@atomicrules.com>
Date: Fri, 17 Feb 2023 16:59:21 -0500
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: be26e898ffb3a1719c88bf025d45a847d3a60ffc
124138-124140 --> 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-17 22:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230217215923.2561685-3-ed.czeck@atomicrules.com>
2023-02-17 21:48 ` qemudev [this message]
2023-02-17 21:52 ` qemudev
2023-02-17 22:00 ` |SUCCESS| pw124140 " checkpatch
2023-02-18 0:39 ` 0-day Robot
2023-02-17 22:29 |SUCCESS| pw124138-124140 [PATCH] [v2, " dpdklab
2023-02-17 22:32 dpdklab
2023-02-17 22:33 dpdklab
2023-02-17 22:40 dpdklab
2023-02-17 22:42 dpdklab
2023-02-17 22:43 dpdklab
2023-02-17 22:45 dpdklab
2023-02-17 22:46 dpdklab
2023-02-17 22:49 dpdklab
2023-02-17 22:53 dpdklab
2023-02-17 23:21 dpdklab
2023-02-17 23:37 dpdklab
2023-02-17 23:46 dpdklab
2023-02-17 23:47 dpdklab
2023-02-17 23:49 dpdklab
2023-02-17 23:50 dpdklab
2023-02-17 23:50 dpdklab
2023-02-17 23:52 dpdklab
2023-02-17 23:52 dpdklab
2023-02-17 23:52 dpdklab
2023-02-18 0:06 dpdklab
2023-02-18 0:08 dpdklab
2023-02-18 0:08 dpdklab
2023-02-18 16:16 dpdklab
2023-02-20 0:57 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=202302172148.31HLm9cB2634674@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).