From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123255 [PATCH v1] Remove Owen Hilyard as a DTS Maintainer
Date: Tue, 7 Feb 2023 22:47:06 +0800 [thread overview]
Message-ID: <202302071447.317El6Rb691217@localhost.localdomain> (raw)
In-Reply-To: <20230207144217.35866-1-ohilyard@iol.unh.edu>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123255
_Compilation OK_
Submitter: Owen Hilyard <ohilyard@iol.unh.edu>
Date: Tue, 7 Feb 2023 09:42:17 -0500
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: a0c837ad1fb5b6a8b10a284ffeb5f9e31bd8ff00
123255 --> 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-02-07 15:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230207144217.35866-1-ohilyard@iol.unh.edu>
2023-02-07 14:43 ` checkpatch
2023-02-07 14:47 ` qemudev [this message]
2023-02-07 14:51 ` qemudev
2023-02-07 16:19 ` 0-day Robot
2023-02-07 15:09 |SUCCESS| pw123255 [PATCH] [v1] " dpdklab
2023-02-07 15:12 dpdklab
2023-02-07 15:13 dpdklab
2023-02-07 15:13 dpdklab
2023-02-07 15:15 dpdklab
2023-02-07 15:19 dpdklab
2023-02-07 15:24 dpdklab
2023-02-07 15:24 dpdklab
2023-02-07 15:25 dpdklab
2023-02-07 15:29 dpdklab
2023-02-07 15:32 dpdklab
2023-02-07 17:44 dpdklab
2023-02-08 6:47 dpdklab
2023-02-08 8:14 dpdklab
2023-02-08 8:14 dpdklab
2023-02-08 8:14 dpdklab
2023-02-08 8:18 dpdklab
2023-02-08 8:18 dpdklab
2023-02-08 8:18 dpdklab
2023-02-08 8:18 dpdklab
2023-02-08 8:18 dpdklab
2023-02-08 8:18 dpdklab
2023-02-08 18:30 dpdklab
2023-02-08 22:35 dpdklab
2023-02-09 8:15 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=202302071447.317El6Rb691217@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).