automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw127084 [PATCH] doc: announce inclusive naming function name changes
Date: Fri, 19 May 2023 14:25:33 +0800	[thread overview]
Message-ID: <202305190625.34J6PXnS3934975@localhost.localdomain> (raw)
In-Reply-To: <20230519063334.1645933-1-chaoyong.he@corigine.com>

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

_Compilation OK_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Fri, 19 May 2023 14:33:34 +0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: a399d7b5a994e335c446d4b15d7622d71dd8848c

127084 --> 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-19  6:39 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230519063334.1645933-1-chaoyong.he@corigine.com>
2023-05-19  6:25 ` qemudev [this message]
2023-05-19  6:29 ` qemudev
2023-05-19  6:37 ` |WARNING| " checkpatch
2023-05-19  7:39 ` |SUCCESS| " 0-day Robot
2023-05-19  9:56 dpdklab
2023-05-19  9:59 dpdklab
2023-05-19 10:02 dpdklab
2023-05-19 10:02 dpdklab
2023-05-19 10:03 dpdklab
2023-05-19 10:16 dpdklab
2023-05-19 10:17 dpdklab
2023-05-19 10:28 dpdklab
2023-05-19 10:28 dpdklab
2023-05-19 10:41 dpdklab
2023-05-19 10:42 dpdklab
2023-05-19 10:45 dpdklab
2023-05-19 10:50 dpdklab
2023-05-19 10:50 dpdklab
2023-05-19 11:04 dpdklab
2023-05-19 11:14 dpdklab
2023-05-19 11:21 dpdklab
2023-05-19 11:28 dpdklab
2023-05-19 11:29 dpdklab
2023-05-19 11:32 dpdklab
2023-05-19 11:34 dpdklab
2023-05-19 11:35 dpdklab
2023-05-19 11:40 dpdklab
2023-05-19 11:42 dpdklab
2023-05-19 18:45 dpdklab
2023-05-19 19:37 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=202305190625.34J6PXnS3934975@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).