From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126073 [PATCH] reorder: improve buffer structure layout
Date: Fri, 14 Apr 2023 16:48:19 +0800 [thread overview]
Message-ID: <202304140848.33E8mJvC908231@localhost.localdomain> (raw)
In-Reply-To: <20230414084344.271602-1-vfialko@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126073
_Compilation OK_
Submitter: Volodymyr Fialko <vfialko@marvell.com>
Date: Fri, 14 Apr 2023 10:43:43 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 3b3fef9de22af80d173453ab65a80b01ce38cbfd
126073 --> 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 prev parent reply other threads:[~2023-04-14 9:02 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230414084344.271602-1-vfialko@marvell.com>
2023-04-14 8:46 ` checkpatch
2023-04-14 8:48 ` qemudev [this message]
2023-04-14 8:52 ` qemudev
2023-04-14 9:59 ` 0-day Robot
2023-04-14 10:47 dpdklab
2023-04-14 10:47 dpdklab
2023-04-14 10:53 dpdklab
2023-04-14 10:53 dpdklab
2023-04-14 10:55 dpdklab
2023-04-14 10:56 dpdklab
2023-04-14 10:59 dpdklab
2023-04-14 11:01 dpdklab
2023-04-14 11:09 dpdklab
2023-04-14 11:13 dpdklab
2023-04-14 11:14 dpdklab
2023-04-14 11:49 dpdklab
2023-04-14 11:50 dpdklab
2023-04-14 11:54 dpdklab
2023-04-14 12:09 dpdklab
2023-04-14 12:11 dpdklab
2023-04-14 12:18 dpdklab
2023-04-14 12:20 dpdklab
2023-04-14 12:24 dpdklab
2023-04-14 12:25 dpdklab
2023-04-14 12:26 dpdklab
2023-04-14 14:54 dpdklab
2023-04-14 15:03 dpdklab
2023-04-14 15:38 dpdklab
2023-04-14 15:39 dpdklab
2023-04-14 23:22 dpdklab
2023-04-14 23:26 dpdklab
2023-04-14 23:32 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=202304140848.33E8mJvC908231@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).