From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw129165 [PATCH] app/testpmd: fix the rule number parsing
Date: Fri, 30 Jun 2023 21:21:14 +0800 [thread overview]
Message-ID: <202306301321.35UDLEg91919830@localhost.localdomain> (raw)
In-Reply-To: <20230630133002.435747-1-bingz@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/129165
_Compilation OK_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Fri, 30 Jun 2023 16:30:02 +0300
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: fb6aeb4e6f518efdf48f6f1edcbada25fd17d0f1
129165 --> 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-06-30 13:35 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230630133002.435747-1-bingz@nvidia.com>
2023-06-30 13:21 ` qemudev [this message]
2023-06-30 13:25 ` qemudev
2023-06-30 13:30 ` |WARNING| " checkpatch
2023-06-30 14:39 ` |SUCCESS| " 0-day Robot
2023-07-01 9:37 dpdklab
2023-07-01 9:38 dpdklab
2023-07-01 9:41 dpdklab
2023-07-01 9:41 dpdklab
2023-07-01 9:42 dpdklab
2023-07-01 9:42 dpdklab
2023-07-01 10:16 dpdklab
2023-07-01 10:22 dpdklab
2023-07-01 10:25 dpdklab
2023-07-01 10:26 dpdklab
2023-07-01 10:28 dpdklab
2023-07-01 10:29 dpdklab
2023-07-01 10:29 dpdklab
2023-07-01 10:30 dpdklab
2023-07-01 10:32 dpdklab
2023-07-01 10:35 dpdklab
2023-07-01 10:36 dpdklab
2023-07-01 11:32 dpdklab
2023-07-01 11:46 dpdklab
2023-07-01 11:47 dpdklab
2023-07-01 15:30 dpdklab
2023-07-01 15:32 dpdklab
2023-07-02 0:23 dpdklab
2023-07-02 0:39 dpdklab
2023-07-02 0:43 dpdklab
2023-07-02 0:51 dpdklab
2023-07-02 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=202306301321.35UDLEg91919830@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).