From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139115 [PATCH] pmdinfogen: avoid empty string in ELFSymbol()
Date: Fri, 5 Apr 2024 19:05:45 +0800 [thread overview]
Message-ID: <202404051105.435B5jqj2736489@localhost.localdomain> (raw)
In-Reply-To: <20240405110929.3279775-1-sebastian.brzezinka@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139115
_Compilation OK_
Submitter: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
Date: Fri, 5 Apr 2024 13:09:29 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139115 --> 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-04-05 11:30 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240405110929.3279775-1-sebastian.brzezinka@intel.com>
2024-04-05 11:05 ` qemudev [this message]
2024-04-05 11:10 ` qemudev
2024-04-05 11:10 ` |SUCCESS| pw139115 [PATCH] pmdinfogen: avoid empty string in ELFSymbol checkpatch
2024-04-05 12:23 ` |SUCCESS| pw139115 [PATCH] pmdinfogen: avoid empty string in ELFSymb dpdklab
2024-04-05 12:27 ` dpdklab
2024-04-05 12:29 ` dpdklab
2024-04-05 12:33 ` dpdklab
2024-04-05 12:40 ` dpdklab
2024-04-05 12:50 ` dpdklab
2024-04-05 12:51 ` dpdklab
2024-04-05 12:51 ` dpdklab
2024-04-05 12:52 ` dpdklab
2024-04-05 12:53 ` dpdklab
2024-04-05 12:53 ` dpdklab
2024-04-05 12:53 ` dpdklab
2024-04-05 12:54 ` dpdklab
2024-04-05 12:55 ` dpdklab
2024-04-05 12:55 ` dpdklab
2024-04-05 12:56 ` dpdklab
2024-04-05 12:56 ` dpdklab
2024-04-05 12:56 ` dpdklab
2024-04-05 12:58 ` dpdklab
2024-04-05 12:59 ` dpdklab
2024-04-05 12:59 ` dpdklab
2024-04-05 13:00 ` dpdklab
2024-04-05 13:00 ` dpdklab
2024-04-05 13:01 ` dpdklab
2024-04-05 13:01 ` dpdklab
2024-04-05 13:01 ` dpdklab
2024-04-05 13:02 ` dpdklab
2024-04-05 13:02 ` dpdklab
2024-04-05 13:02 ` dpdklab
2024-04-05 13:03 ` dpdklab
2024-04-05 13:04 ` dpdklab
2024-04-05 13:04 ` dpdklab
2024-04-05 13:05 ` dpdklab
2024-04-05 13:05 ` dpdklab
2024-04-05 13:06 ` dpdklab
2024-04-05 13:06 ` dpdklab
2024-04-05 13:06 ` dpdklab
2024-04-05 13:07 ` dpdklab
2024-04-05 13:07 ` dpdklab
2024-04-05 13:07 ` dpdklab
2024-04-05 13:09 ` dpdklab
2024-04-05 13:09 ` dpdklab
2024-04-05 13:10 ` dpdklab
2024-04-05 13:10 ` dpdklab
2024-04-05 13:10 ` dpdklab
2024-04-05 13:10 ` dpdklab
2024-04-05 13:11 ` dpdklab
2024-04-05 13:11 ` dpdklab
2024-04-05 13:12 ` dpdklab
2024-04-05 13:12 ` dpdklab
2024-04-05 13:12 ` dpdklab
2024-04-05 13:13 ` dpdklab
2024-04-05 13:14 ` dpdklab
2024-04-05 13:14 ` dpdklab
2024-04-05 13:16 ` dpdklab
2024-04-05 13:16 ` dpdklab
2024-04-05 13:17 ` dpdklab
2024-04-05 13:17 ` dpdklab
2024-04-05 13:19 ` dpdklab
2024-04-05 13:20 ` dpdklab
2024-04-05 13:21 ` dpdklab
2024-04-05 13:22 ` dpdklab
2024-04-05 13:22 ` dpdklab
2024-04-05 13:23 ` dpdklab
2024-04-05 13:25 ` dpdklab
2024-04-05 13:25 ` dpdklab
2024-04-05 13:26 ` dpdklab
2024-04-05 13:26 ` dpdklab
2024-04-05 13:26 ` dpdklab
2024-04-05 13:26 ` dpdklab
2024-04-05 13:27 ` dpdklab
2024-04-05 13:27 ` dpdklab
2024-04-05 13:29 ` dpdklab
2024-04-05 13:30 ` dpdklab
2024-04-05 13:30 ` dpdklab
2024-04-05 13:30 ` dpdklab
2024-04-05 13:38 ` dpdklab
2024-04-05 13:42 ` dpdklab
2024-04-05 13:44 ` dpdklab
2024-04-05 13:45 ` dpdklab
2024-04-05 13:52 ` dpdklab
2024-04-05 13:56 ` dpdklab
2024-04-05 13:56 ` dpdklab
2024-04-05 14:01 ` dpdklab
2024-04-05 14:06 ` dpdklab
2024-04-05 14:29 ` dpdklab
2024-04-05 14:59 ` dpdklab
2024-04-05 15:57 ` 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=202404051105.435B5jqj2736489@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).