From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123175 [PATCH v3] app/procinfo: display eventdev xstats for PMD data
Date: Tue, 7 Feb 2023 07:12:19 +0800 [thread overview]
Message-ID: <202302062312.316NCJ0E3723920@localhost.localdomain> (raw)
In-Reply-To: <20230206230505.3029148-1-abdullah.sevincer@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123175
_Compilation OK_
Submitter: Abdullah Sevincer <abdullah.sevincer@intel.com>
Date: Mon, 6 Feb 2023 17:05:05 -0600
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: d3802886aaa76604833da59fa2df7cd519e59982
123175 --> 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 prev parent reply other threads:[~2023-02-06 23:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230206230505.3029148-1-abdullah.sevincer@intel.com>
2023-02-06 23:05 ` checkpatch
2023-02-06 23:12 ` qemudev [this message]
2023-02-06 23:16 ` qemudev
2023-02-06 23:59 ` |FAILURE| " 0-day Robot
2023-02-07 20:15 |SUCCESS| pw123175 [PATCH] [v3] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-02-07 16:08 dpdklab
2023-02-07 13:55 dpdklab
2023-02-07 8:38 dpdklab
2023-02-07 8:37 dpdklab
2023-02-07 8:37 dpdklab
2023-02-07 8:37 dpdklab
2023-02-07 8:37 dpdklab
2023-02-07 8:35 dpdklab
2023-02-07 8:35 dpdklab
2023-02-07 8:35 dpdklab
2023-02-07 7:17 dpdklab
2023-02-07 0:55 dpdklab
2023-02-06 23:51 dpdklab
2023-02-06 23:47 dpdklab
2023-02-06 23:44 dpdklab
2023-02-06 23:44 dpdklab
2023-02-06 23:43 dpdklab
2023-02-06 23:40 dpdklab
2023-02-06 23:39 dpdklab
2023-02-06 23:37 dpdklab
2023-02-06 23:35 dpdklab
2023-02-06 23:34 dpdklab
2023-02-06 23:32 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=202302062312.316NCJ0E3723920@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).