From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126264 [PATCH] devtools: add script to check for non inclusive naming
Date: Wed, 19 Apr 2023 22:52:09 +0800 [thread overview]
Message-ID: <202304191452.33JEq9wP1936288@localhost.localdomain> (raw)
In-Reply-To: <20230419150020.65805-1-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126264
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wed, 19 Apr 2023 08:00:20 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 3b3fef9de22af80d173453ab65a80b01ce38cbfd
126264 --> 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-19 15:06 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230419150020.65805-1-stephen@networkplumber.org>
2023-04-19 14:52 ` qemudev [this message]
2023-04-19 14:56 ` qemudev
2023-04-19 15:02 ` |WARNING| " checkpatch
2023-04-19 15:59 ` |SUCCESS| " 0-day Robot
2023-04-19 15:26 dpdklab
2023-04-19 15:33 dpdklab
2023-04-19 15:33 dpdklab
2023-04-19 15:37 dpdklab
2023-04-19 15:38 dpdklab
2023-04-19 15:41 dpdklab
2023-04-19 15:41 dpdklab
2023-04-19 15:41 dpdklab
2023-04-19 15:46 dpdklab
2023-04-19 15:46 dpdklab
2023-04-19 15:46 dpdklab
2023-04-19 15:50 dpdklab
2023-04-19 15:54 dpdklab
2023-04-19 15:58 dpdklab
2023-04-19 16:01 dpdklab
2023-04-19 16:08 dpdklab
2023-04-19 16:08 dpdklab
2023-04-19 16:08 dpdklab
2023-04-19 16:08 dpdklab
2023-04-19 16:09 dpdklab
2023-04-19 16:12 dpdklab
2023-04-19 16:24 dpdklab
2023-04-19 16:29 dpdklab
2023-04-19 16:30 dpdklab
2023-04-19 16:35 dpdklab
2023-04-19 18:53 dpdklab
2023-04-19 18:54 dpdklab
2023-04-19 18:59 dpdklab
2023-04-19 19:04 dpdklab
2023-04-19 19:35 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=202304191452.33JEq9wP1936288@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).