From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw120906-120907 [PATCH 2/2] app/testpmd: add disable-flow-flush parameter
Date: Thu, 15 Dec 2022 09:42:18 +0800 [thread overview]
Message-ID: <202212150142.2BF1gIHe3405152@localhost.localdomain> (raw)
In-Reply-To: <20221215014142.15750-3-fengchengwen@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/120907
_Compilation OK_
Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Thu, 15 Dec 2022 01:41:41 +0000
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 9351bc0906b4585fd9d50a89f9f6d2f091d3e822
120906-120907 --> 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:[~2022-12-15 1:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221215014142.15750-3-fengchengwen@huawei.com>
2022-12-15 1:42 ` qemudev [this message]
2022-12-15 1:46 ` qemudev
2022-12-15 1:49 ` |WARNING| pw120907 " checkpatch
2022-12-15 2:38 ` |SUCCESS| " 0-day Robot
2022-12-15 2:20 |SUCCESS| pw120906-120907 [PATCH] [2/2] " dpdklab
2022-12-15 2:20 dpdklab
2022-12-15 2:21 dpdklab
2022-12-15 2:24 dpdklab
2022-12-15 2:25 dpdklab
2022-12-15 2:32 dpdklab
2022-12-15 2:45 dpdklab
2022-12-15 2:45 dpdklab
2022-12-15 2:52 dpdklab
2022-12-15 2:58 dpdklab
2022-12-15 3:06 dpdklab
2022-12-15 3:09 dpdklab
2022-12-15 3:12 dpdklab
2022-12-15 3:18 dpdklab
2022-12-15 3:19 dpdklab
2022-12-15 3:20 dpdklab
2022-12-15 3:21 dpdklab
2022-12-15 3:33 dpdklab
2022-12-15 3:35 dpdklab
2022-12-15 3:39 dpdklab
2022-12-15 3:40 dpdklab
2022-12-15 3:41 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=202212150142.2BF1gIHe3405152@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).