automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139200-139207 [PATCH v8 8/8] doc: update documentation of TAP PMD
Date: Tue, 9 Apr 2024 11:21:41 +0800	[thread overview]
Message-ID: <202404090321.4393Lf0R043273@localhost.localdomain> (raw)
In-Reply-To: <20240409034237.433270-9-stephen@networkplumber.org>

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

_Compilation OK_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Mon,  8 Apr 2024 20:40:30 -0700
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c

139200-139207 --> 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-04-09  3:46 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240409034237.433270-9-stephen@networkplumber.org>
2024-04-09  3:21 ` qemudev [this message]
2024-04-09  3:26 ` qemudev
2024-04-09  3:43 ` |SUCCESS| pw139207 " checkpatch
2024-04-09  4:44 ` 0-day Robot
2024-04-09  5:20 ` |SUCCESS| pw139200-139207 [PATCH] [v8,8/8] doc: update documentation dpdklab
2024-04-09  5:22 ` dpdklab
2024-04-09  5:33 ` dpdklab
2024-04-09  5:34 ` dpdklab
2024-04-09  5:34 ` dpdklab
2024-04-09  5:44 ` dpdklab
2024-04-09  5:46 ` dpdklab
2024-04-09  5:49 ` dpdklab
2024-04-09  5:49 ` dpdklab
2024-04-09  5:50 ` dpdklab
2024-04-09  5:51 ` dpdklab
2024-04-09  5:51 ` dpdklab
2024-04-09  5:52 ` dpdklab
2024-04-09  6:41 ` dpdklab
2024-04-09  6:43 ` dpdklab
2024-04-09  6:47 ` dpdklab
2024-04-09  6:48 ` dpdklab
2024-04-09  6:49 ` dpdklab
2024-04-09  6:49 ` dpdklab
2024-04-09  6:49 ` dpdklab
2024-04-09  6:50 ` dpdklab
2024-04-09  6:51 ` dpdklab
2024-04-09  6:51 ` dpdklab
2024-04-09  6:52 ` dpdklab
2024-04-09  6:52 ` dpdklab
2024-04-09  6:52 ` dpdklab
2024-04-09  6:54 ` dpdklab
2024-04-09  6:56 ` dpdklab
2024-04-09  6:57 ` dpdklab
2024-04-09  6:57 ` dpdklab
2024-04-09  6:59 ` dpdklab
2024-04-09  6:59 ` dpdklab
2024-04-09  7:10 ` dpdklab
2024-04-09  7:10 ` dpdklab
2024-04-09  7:14 ` dpdklab
2024-04-09  7:15 ` dpdklab
2024-04-09  7:16 ` dpdklab
2024-04-09  7:17 ` dpdklab
2024-04-09  7:18 ` dpdklab
2024-04-09  7:19 ` dpdklab
2024-04-09  7:20 ` dpdklab
2024-04-09  7:20 ` dpdklab
2024-04-09  7:21 ` dpdklab
2024-04-09  7:21 ` dpdklab
2024-04-09  7:32 ` dpdklab
2024-04-09  7:35 ` dpdklab
2024-04-09  7:35 ` dpdklab
2024-04-09  7:35 ` dpdklab
2024-04-09  7:43 ` dpdklab
2024-04-09  7:44 ` dpdklab
2024-04-09  7:45 ` dpdklab
2024-04-09  7:45 ` dpdklab
2024-04-09  7:45 ` dpdklab
2024-04-09  7:46 ` dpdklab
2024-04-09  7:46 ` dpdklab
2024-04-09  7:47 ` dpdklab
2024-04-09  7:47 ` dpdklab
2024-04-09  7:55 ` dpdklab
2024-04-09  7:55 ` dpdklab
2024-04-09  8:19 ` dpdklab
2024-04-09  8:20 ` dpdklab
2024-04-09  8:21 ` dpdklab
2024-04-09  8:21 ` dpdklab
2024-04-09  8:23 ` dpdklab
2024-04-09  8:23 ` dpdklab
2024-04-09  8:24 ` dpdklab
2024-04-09  8:24 ` dpdklab
2024-04-09  8:25 ` dpdklab
2024-04-09  8:26 ` dpdklab
2024-04-09  8:26 ` dpdklab
2024-04-09  8:26 ` dpdklab
2024-04-09  8:27 ` dpdklab
2024-04-09  8:29 ` dpdklab
2024-04-09  8:30 ` dpdklab
2024-04-09  8:31 ` dpdklab
2024-04-09  8:45 ` dpdklab
2024-04-09  9:01 ` dpdklab
2024-04-09  9:05 ` dpdklab
2024-04-09  9:08 ` dpdklab
2024-04-09  9:11 ` dpdklab
2024-04-09  9:12 ` dpdklab
2024-04-09  9:14 ` dpdklab
2024-04-09  9:15 ` dpdklab
2024-04-09  9:30 ` dpdklab
2024-04-09  9:35 ` dpdklab
2024-04-09  9:39 ` dpdklab
2024-04-09  9:48 ` dpdklab
2024-04-09 14:26 ` |WARNING| " 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=202404090321.4393Lf0R043273@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).