From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw147243 [PATCH] net/i40e/base: fix invalid log format characters
Date: Fri, 25 Oct 2024 19:57:08 +0800 [thread overview]
Message-ID: <202410251157.49PBv8Hi121128@localhost.localdomain> (raw)
In-Reply-To: <20241025122746.1775593-1-bruce.richardson@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/147243
_Compilation OK_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Fri, 25 Oct 2024 13:27:46 +0100
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 69c0ffb893fa9c1c7b00947a2801cef50ebc65d4
147243 --> 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:[~2024-10-25 12:31 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241025122746.1775593-1-bruce.richardson@intel.com>
2024-10-25 11:57 ` qemudev [this message]
2024-10-25 12:01 ` qemudev
2024-10-25 12:29 ` |WARNING| " checkpatch
2024-10-25 13:26 ` |SUCCESS| " 0-day Robot
2024-10-25 17:51 ` |SUCCESS| pw147243 [PATCH] net/i40e/base: fix invalid log format cha dpdklab
2024-10-25 18:11 ` dpdklab
2024-10-25 19:08 ` dpdklab
2024-10-25 19:23 ` dpdklab
2024-10-25 19:29 ` dpdklab
2024-10-25 19:43 ` dpdklab
2024-10-25 19:56 ` dpdklab
2024-10-25 20:16 ` dpdklab
2024-10-25 20:31 ` dpdklab
2024-10-25 21:06 ` dpdklab
2024-10-26 10:12 ` dpdklab
2024-10-26 10:32 ` dpdklab
2024-10-27 0:13 ` dpdklab
2024-10-27 0:48 ` dpdklab
2024-10-27 1:05 ` dpdklab
2024-10-27 1:40 ` dpdklab
2024-10-30 2:27 ` dpdklab
2024-10-30 2:46 ` dpdklab
2024-10-30 2:56 ` dpdklab
2024-10-30 2:56 ` dpdklab
2024-10-30 4:15 ` dpdklab
2024-10-30 4:58 ` dpdklab
2024-10-30 5:58 ` |PENDING| " dpdklab
2024-10-30 6:01 ` dpdklab
2024-10-30 6:29 ` |SUCCESS| " dpdklab
2024-10-30 7:21 ` dpdklab
2024-10-30 9:20 ` |PENDING| " dpdklab
2024-10-30 10:39 ` |FAILURE| " dpdklab
2024-10-30 10:39 ` dpdklab
2024-10-30 11:36 ` |WARNING| " dpdklab
2024-10-30 12:39 ` |SUCCESS| " dpdklab
2024-10-30 12:54 ` |PENDING| " dpdklab
2024-10-30 13:22 ` |WARNING| " dpdklab
2024-10-30 13:38 ` |SUCCESS| " dpdklab
2024-10-31 1:28 ` dpdklab
2024-10-31 4:43 ` dpdklab
2024-11-01 21:15 ` dpdklab
2024-11-02 9:05 ` dpdklab
2024-11-02 9:43 ` dpdklab
2024-11-02 9:49 ` dpdklab
2024-11-03 18:56 ` 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=202410251157.49PBv8Hi121128@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).