From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw131145 [PATCH] clarify purpose of empty cache lines
Date: Mon, 4 Sep 2023 16:41:10 +0800 [thread overview]
Message-ID: <202309040841.3848fAus3876990@localhost.localdomain> (raw)
In-Reply-To: <20230904084349.12044-1-mb@smartsharesystems.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/131145
_Compilation OK_
Submitter: Morten Brørup <mb@smartsharesystems.com>
Date: Mon, 4 Sep 2023 10:43:49 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 799d56f1192d72872e63fbb3d2c7f776b7ae89b0
131145 --> 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-09-04 8:55 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230904084349.12044-1-mb@smartsharesystems.com>
2023-09-04 8:41 ` qemudev [this message]
2023-09-04 8:44 ` |WARNING| " checkpatch
2023-09-04 8:45 ` |SUCCESS| " qemudev
2023-09-04 9:59 ` 0-day Robot
2023-09-04 10:14 dpdklab
2023-09-04 10:15 dpdklab
2023-09-04 10:16 dpdklab
2023-09-04 10:16 dpdklab
2023-09-04 10:19 dpdklab
2023-09-04 10:19 dpdklab
2023-09-04 10:20 dpdklab
2023-09-04 10:23 dpdklab
2023-09-04 10:24 dpdklab
2023-09-04 10:26 dpdklab
2023-09-04 10:29 dpdklab
2023-09-04 10:30 dpdklab
2023-09-04 10:31 dpdklab
2023-09-04 10:32 dpdklab
2023-09-04 10:32 dpdklab
2023-09-04 10:34 dpdklab
2023-09-04 10:35 dpdklab
2023-09-04 10:48 dpdklab
2023-09-04 10:56 dpdklab
2023-09-04 10:57 dpdklab
2023-09-04 10:58 dpdklab
2023-09-04 11:00 dpdklab
2023-09-04 11:02 dpdklab
2023-09-04 11:04 dpdklab
2023-09-04 11:06 dpdklab
2023-09-04 11:06 dpdklab
2023-09-04 11:06 dpdklab
2023-09-04 11:06 dpdklab
2023-09-04 11:06 dpdklab
2023-09-04 11:07 dpdklab
2023-09-04 11:09 dpdklab
2023-09-04 11:09 dpdklab
2023-09-04 11:10 dpdklab
2023-09-04 11:15 dpdklab
2023-09-04 11:17 dpdklab
2023-09-04 11:20 dpdklab
2023-09-04 11:21 dpdklab
2023-09-04 11:31 dpdklab
2023-09-04 11:32 dpdklab
2023-09-04 11:43 dpdklab
2023-09-04 11:54 dpdklab
2023-09-04 12:02 dpdklab
2023-09-04 12:02 dpdklab
2023-09-04 12:03 dpdklab
2023-09-04 12:05 dpdklab
2023-09-05 15:06 dpdklab
2023-09-05 15:11 dpdklab
2023-09-05 15:15 dpdklab
2023-09-05 15:16 dpdklab
2023-09-06 2:29 dpdklab
2023-09-06 2:34 dpdklab
2023-09-06 2:40 dpdklab
2023-09-06 2:51 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=202309040841.3848fAus3876990@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).