automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw135818 [PATCH] doc: add testpmd latencystats option
Date: Wed, 10 Jan 2024 07:01:40 +0800	[thread overview]
Message-ID: <202401092301.409N1eW83772576@localhost.localdomain> (raw)
In-Reply-To: <20240109230849.6348-1-stephen@networkplumber.org>

Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/135818

_Compilation OK_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tue,  9 Jan 2024 15:08:49 -0800
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 98ab16778daaa6965e9a95678c53761b473acecf

135818 --> 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


       reply	other threads:[~2024-01-09 23:22 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240109230849.6348-1-stephen@networkplumber.org>
2024-01-09 23:01 ` qemudev [this message]
2024-01-09 23:05 ` qemudev
2024-01-09 23:09 ` checkpatch
2024-01-10  0:26 ` 0-day Robot
2024-01-10  0:17 dpdklab
2024-01-10  0:17 dpdklab
2024-01-10  0:18 dpdklab
2024-01-10  0:19 dpdklab
2024-01-10  0:30 dpdklab
2024-01-10  0:31 dpdklab
2024-01-10  0:31 dpdklab
2024-01-10  0:32 dpdklab
2024-01-10  0:32 dpdklab
2024-01-10  0:32 dpdklab
2024-01-10  0:32 dpdklab
2024-01-10  0:33 dpdklab
2024-01-10  0:33 dpdklab
2024-01-10  0:34 dpdklab
2024-01-10  0:34 dpdklab
2024-01-10  0:34 dpdklab
2024-01-10  0:34 dpdklab
2024-01-10  0:35 dpdklab
2024-01-10  0:35 dpdklab
2024-01-10  0:35 dpdklab
2024-01-10  0:35 dpdklab
2024-01-10  0:35 dpdklab
2024-01-10  0:36 dpdklab
2024-01-10  0:36 dpdklab
2024-01-10  0:37 dpdklab
2024-01-10  0:37 dpdklab
2024-01-10  0:38 dpdklab
2024-01-10  0:38 dpdklab
2024-01-10  0:39 dpdklab
2024-01-10  0:39 dpdklab
2024-01-10  0:40 dpdklab
2024-01-10  0:40 dpdklab
2024-01-10  0:40 dpdklab
2024-01-10  0:41 dpdklab
2024-01-10  0:41 dpdklab
2024-01-10  0:41 dpdklab
2024-01-10  0:41 dpdklab
2024-01-10  0:42 dpdklab
2024-01-10  0:42 dpdklab
2024-01-10  0:42 dpdklab
2024-01-10  0:43 dpdklab
2024-01-10  0:43 dpdklab
2024-01-10  0:44 dpdklab
2024-01-10  0:44 dpdklab
2024-01-10  0:45 dpdklab
2024-01-10  0:46 dpdklab
2024-01-10  0:47 dpdklab
2024-01-10  0:48 dpdklab
2024-01-10  0:48 dpdklab
2024-01-10  0:50 dpdklab
2024-01-10  0:52 dpdklab
2024-01-10  0:53 dpdklab
2024-01-10  0:53 dpdklab
2024-01-10  0:53 dpdklab
2024-01-10  0:53 dpdklab
2024-01-10  0:53 dpdklab
2024-01-10  0:54 dpdklab
2024-01-10  0:54 dpdklab
2024-01-10  0:56 dpdklab
2024-01-10  1:01 dpdklab
2024-01-10  1:02 dpdklab
2024-01-10  1:03 dpdklab
2024-01-10  1:05 dpdklab
2024-01-10  1:13 dpdklab
2024-01-10  2:05 dpdklab
2024-01-10  2:09 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=202401092301.409N1eW83772576@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).