automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw141508 [PATCH] app/testpmd: fix help string of BPF load command
Date: Mon, 24 Jun 2024 09:35:03 +0800	[thread overview]
Message-ID: <202406240135.45O1Z3nb1168003@localhost.localdomain> (raw)
In-Reply-To: <20240624015852.3712910-1-chaoyong.he@corigine.com>

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

_Compilation OK_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Mon, 24 Jun 2024 09:58:52 +0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 4a44d97f0a52a76258c6a6cb6a713f4380a8ab1f

141508 --> 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-06-24  2:03 UTC|newest]

Thread overview: 114+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240624015852.3712910-1-chaoyong.he@corigine.com>
2024-06-24  1:35 ` qemudev [this message]
2024-06-24  1:39 ` qemudev
2024-06-24  2:01 ` checkpatch
2024-06-24  2:47 ` |SUCCESS| pw141508 [PATCH] app/testpmd: fix help string of BPF load dpdklab
2024-06-24  2:47 ` dpdklab
2024-06-24  2:48 ` dpdklab
2024-06-24  2:48 ` dpdklab
2024-06-24  2:48 ` dpdklab
2024-06-24  2:49 ` dpdklab
2024-06-24  2:49 ` dpdklab
2024-06-24  2:49 ` dpdklab
2024-06-24  2:49 ` dpdklab
2024-06-24  2:50 ` dpdklab
2024-06-24  2:50 ` dpdklab
2024-06-24  2:50 ` dpdklab
2024-06-24  2:51 ` dpdklab
2024-06-24  2:51 ` dpdklab
2024-06-24  2:51 ` dpdklab
2024-06-24  2:51 ` dpdklab
2024-06-24  2:52 ` dpdklab
2024-06-24  2:52 ` dpdklab
2024-06-24  2:52 ` dpdklab
2024-06-24  2:52 ` dpdklab
2024-06-24  2:53 ` dpdklab
2024-06-24  2:53 ` dpdklab
2024-06-24  2:53 ` dpdklab
2024-06-24  2:54 ` dpdklab
2024-06-24  2:54 ` dpdklab
2024-06-24  2:54 ` dpdklab
2024-06-24  2:54 ` dpdklab
2024-06-24  2:55 ` dpdklab
2024-06-24  2:55 ` dpdklab
2024-06-24  2:55 ` dpdklab
2024-06-24  2:55 ` dpdklab
2024-06-24  2:55 ` dpdklab
2024-06-24  2:55 ` dpdklab
2024-06-24  2:56 ` dpdklab
2024-06-24  2:56 ` dpdklab
2024-06-24  2:56 ` dpdklab
2024-06-24  2:56 ` dpdklab
2024-06-24  2:57 ` dpdklab
2024-06-24  2:57 ` dpdklab
2024-06-24  2:58 ` dpdklab
2024-06-24  2:58 ` dpdklab
2024-06-24  2:58 ` dpdklab
2024-06-24  2:58 ` dpdklab
2024-06-24  2:59 ` dpdklab
2024-06-24  2:59 ` dpdklab
2024-06-24  2:59 ` dpdklab
2024-06-24  2:59 ` dpdklab
2024-06-24  2:59 ` dpdklab
2024-06-24  3:00 ` dpdklab
2024-06-24  3:00 ` dpdklab
2024-06-24  3:00 ` dpdklab
2024-06-24  3:01 ` dpdklab
2024-06-24  3:02 ` dpdklab
2024-06-24  3:02 ` dpdklab
2024-06-24  3:03 ` dpdklab
2024-06-24  3:03 ` dpdklab
2024-06-24  3:04 ` dpdklab
2024-06-24  3:04 ` |SUCCESS| pw141508 [PATCH] app/testpmd: fix help string of BPF load command 0-day Robot
2024-06-24  3:04 ` |SUCCESS| pw141508 [PATCH] app/testpmd: fix help string of BPF load dpdklab
2024-06-24  3:04 ` dpdklab
2024-06-24  3:05 ` dpdklab
2024-06-24  3:05 ` dpdklab
2024-06-24  3:06 ` dpdklab
2024-06-24  3:06 ` dpdklab
2024-06-24  3:07 ` dpdklab
2024-06-24  3:07 ` dpdklab
2024-06-24  3:08 ` dpdklab
2024-06-24  3:09 ` dpdklab
2024-06-24  3:09 ` dpdklab
2024-06-24  3:10 ` dpdklab
2024-06-24  3:11 ` dpdklab
2024-06-24  3:11 ` dpdklab
2024-06-24  3:12 ` dpdklab
2024-06-24  3:13 ` dpdklab
2024-06-24  3:14 ` dpdklab
2024-06-24  3:14 ` dpdklab
2024-06-24  3:14 ` dpdklab
2024-06-24  3:15 ` dpdklab
2024-06-24  3:15 ` dpdklab
2024-06-24  3:20 ` dpdklab
2024-06-24  3:20 ` dpdklab
2024-06-24  3:20 ` dpdklab
2024-06-24  3:22 ` dpdklab
2024-06-24  3:22 ` dpdklab
2024-06-24  3:23 ` dpdklab
2024-06-24  3:23 ` dpdklab
2024-06-24  3:24 ` dpdklab
2024-06-24  3:24 ` dpdklab
2024-06-24  3:25 ` dpdklab
2024-06-24  3:27 ` dpdklab
2024-06-24  3:27 ` dpdklab
2024-06-24  3:27 ` dpdklab
2024-06-24  3:28 ` dpdklab
2024-06-24  3:28 ` dpdklab
2024-06-24  3:29 ` dpdklab
2024-06-24  3:29 ` dpdklab
2024-06-24  3:31 ` dpdklab
2024-06-24  3:33 ` dpdklab
2024-06-24  3:33 ` dpdklab
2024-06-24  3:35 ` dpdklab
2024-06-24  3:35 ` dpdklab
2024-06-24  3:36 ` dpdklab
2024-06-24  3:36 ` dpdklab
2024-06-24  3:37 ` dpdklab
2024-06-24  3:39 ` dpdklab
2024-06-24  3:40 ` dpdklab
2024-06-24  3:43 ` dpdklab
2024-06-24  3:44 ` dpdklab
2024-06-24  3:58 ` dpdklab
2024-06-24  4:01 ` dpdklab
2024-06-24  5:12 ` 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=202406240135.45O1Z3nb1168003@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).