From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122124-122130 [PATCH v2 7/7] ip_frag: fix whitespace
Date: Tue, 17 Jan 2023 01:44:59 +0800 [thread overview]
Message-ID: <202301161744.30GHixUk1186049@localhost.localdomain> (raw)
In-Reply-To: <20230116175127.87346-8-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/122130
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Mon, 16 Jan 2023 09:51:21 -0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 83397b9f073904438965e1fda2efe76f7850fe01
122124-122130 --> 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-01-16 17:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230116175127.87346-8-stephen@networkplumber.org>
2023-01-16 17:44 ` qemudev [this message]
2023-01-16 17:48 ` qemudev
2023-01-16 17:52 ` |SUCCESS| pw122130 " checkpatch
2023-01-16 18:39 ` |FAILURE| " 0-day Robot
2023-01-16 18:25 |SUCCESS| pw122124-122130 [PATCH] [v2,7/7] " dpdklab
2023-01-16 18:28 dpdklab
2023-01-16 18:29 dpdklab
2023-01-16 18:33 dpdklab
2023-01-16 18:47 dpdklab
2023-01-16 18:55 dpdklab
2023-01-16 19:03 dpdklab
2023-01-16 19:15 dpdklab
2023-01-16 20:29 dpdklab
2023-01-16 22:36 dpdklab
2023-01-16 22:47 dpdklab
2023-01-16 22:47 dpdklab
2023-01-16 22:48 dpdklab
2023-01-16 22:48 dpdklab
2023-01-16 22:48 dpdklab
2023-01-16 22:48 dpdklab
2023-01-16 22:48 dpdklab
2023-01-16 22:48 dpdklab
2023-01-16 22:48 dpdklab
2023-01-17 0:17 dpdklab
2023-01-17 0:29 dpdklab
2023-01-17 1:03 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=202301161744.30GHixUk1186049@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).