automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126678 [PATCH] doc: fix typo in graph lib doc
Date: Thu, 4 May 2023 12:21:20 +0800	[thread overview]
Message-ID: <202305040421.3444LKgW215415@localhost.localdomain> (raw)
In-Reply-To: <20230504043135.3977224-1-asekhar@marvell.com>

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

_Compilation OK_

Submitter: Ashwin Sekhar T K <asekhar@marvell.com>
Date: Thu, 4 May 2023 10:01:35 +0530
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: d03446724972d2a1bb645ce7f3e64f5ef0203d61

126678 --> 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:[~2023-05-04  4:35 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230504043135.3977224-1-asekhar@marvell.com>
2023-05-04  4:21 ` qemudev [this message]
2023-05-04  4:25 ` qemudev
2023-05-04  4:32 ` checkpatch
2023-05-04  5:40 ` 0-day Robot
2023-05-04  5:12 dpdklab
2023-05-04  5:19 dpdklab
2023-05-04  5:19 dpdklab
2023-05-04  5:19 dpdklab
2023-05-04  5:22 dpdklab
2023-05-04  5:30 dpdklab
2023-05-04  5:38 dpdklab
2023-05-04  5:43 dpdklab
2023-05-04  5:54 dpdklab
2023-05-04  5:56 dpdklab
2023-05-04  6:02 dpdklab
2023-05-04  6:07 dpdklab
2023-05-04  6:11 dpdklab
2023-05-04  6:38 dpdklab
2023-05-04  6:48 dpdklab
2023-05-04  6:48 dpdklab
2023-05-04  6:54 dpdklab
2023-05-04  6:56 dpdklab
2023-05-04  6:59 dpdklab
2023-05-04  7:03 dpdklab
2023-05-04  7:07 dpdklab
2023-05-04  7:07 dpdklab
2023-05-04  7:10 dpdklab
2023-05-04  7:22 dpdklab
2023-05-04  7:23 dpdklab
2023-05-04  7:24 dpdklab
2023-05-04  7:30 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=202305040421.3444LKgW215415@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).