automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138741 [PATCH] Spelling : Fix spelling mistake.
Date: Fri, 22 Mar 2024 21:03:24 +0800	[thread overview]
Message-ID: <202403221303.42MD3ORN1732272@localhost.localdomain> (raw)
In-Reply-To: <PH7PR20MB546848979319542BEB6BB722E8322@PH7PR20MB5468.namprd20.prod.outlook.com>

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

_Compilation OK_

Submitter: Fidel Castro <fidelcastro.s@hotmail.com>
Date: Thu, 21 Mar 2024 18:35:52 -0400
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 0219d467bcb1d19b386b5bae8eecd3514ba13fdb

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


  parent reply	other threads:[~2024-03-22 13:28 UTC|newest]

Thread overview: 82+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <PH7PR20MB546848979319542BEB6BB722E8322@PH7PR20MB5468.namprd20.prod.outlook.com>
2024-03-22 12:50 ` checkpatch
2024-03-22 13:03 ` qemudev [this message]
2024-03-22 13:08 ` qemudev
2024-03-22 16:45 ` 0-day Robot
2024-03-22 22:04 ` dpdklab
2024-03-22 22:23 ` dpdklab
2024-03-22 22:46 ` dpdklab
2024-03-22 22:47 ` dpdklab
2024-03-22 22:52 ` dpdklab
2024-03-22 23:01 ` dpdklab
2024-03-22 23:03 ` dpdklab
2024-03-22 23:05 ` dpdklab
2024-03-22 23:07 ` dpdklab
2024-03-22 23:07 ` dpdklab
2024-03-22 23:09 ` dpdklab
2024-03-22 23:16 ` dpdklab
2024-03-22 23:16 ` dpdklab
2024-03-22 23:17 ` dpdklab
2024-03-22 23:18 ` dpdklab
2024-03-22 23:42 ` dpdklab
2024-03-22 23:50 ` dpdklab
2024-03-22 23:56 ` dpdklab
2024-03-22 23:57 ` dpdklab
2024-03-23  0:01 ` dpdklab
2024-03-23  0:01 ` dpdklab
2024-03-23  0:03 ` dpdklab
2024-03-23  0:04 ` dpdklab
2024-03-23  0:05 ` dpdklab
2024-03-23  0:08 ` dpdklab
2024-03-23  0:08 ` dpdklab
2024-03-23  0:09 ` dpdklab
2024-03-23  0:09 ` dpdklab
2024-03-23  0:09 ` dpdklab
2024-03-23  0:11 ` dpdklab
2024-03-23  0:11 ` dpdklab
2024-03-23  0:12 ` dpdklab
2024-03-23  0:12 ` dpdklab
2024-03-23  0:12 ` dpdklab
2024-03-23  0:13 ` dpdklab
2024-03-23  0:13 ` dpdklab
2024-03-23  0:13 ` dpdklab
2024-03-23  0:14 ` dpdklab
2024-03-23  0:14 ` dpdklab
2024-03-23  0:15 ` dpdklab
2024-03-23  0:15 ` dpdklab
2024-03-23  0:15 ` dpdklab
2024-03-23  0:17 ` dpdklab
2024-03-23  0:17 ` dpdklab
2024-03-23  0:17 ` dpdklab
2024-03-23  0:18 ` dpdklab
2024-03-23  0:18 ` dpdklab
2024-03-23  0:19 ` dpdklab
2024-03-23  0:19 ` dpdklab
2024-03-23  0:19 ` dpdklab
2024-03-23  0:19 ` dpdklab
2024-03-23  0:19 ` dpdklab
2024-03-23  0:20 ` dpdklab
2024-03-23  0:20 ` dpdklab
2024-03-23  0:20 ` dpdklab
2024-03-23  0:20 ` dpdklab
2024-03-23  0:20 ` dpdklab
2024-03-23  0:21 ` dpdklab
2024-03-23  0:21 ` dpdklab
2024-03-23  0:21 ` dpdklab
2024-03-23  0:21 ` dpdklab
2024-03-23  0:21 ` dpdklab
2024-03-23  0:21 ` dpdklab
2024-03-23  0:23 ` dpdklab
2024-03-23  0:23 ` dpdklab
2024-03-23  0:23 ` dpdklab
2024-03-23  0:23 ` dpdklab
2024-03-23  0:24 ` dpdklab
2024-03-23  0:24 ` dpdklab
2024-03-23  0:24 ` dpdklab
2024-03-23  0:37 ` dpdklab
2024-03-23  0:38 ` dpdklab
2024-03-23  1:14 ` dpdklab
2024-03-23  2:17 ` dpdklab
2024-03-23  2:30 ` dpdklab
2024-03-23  4:23 ` dpdklab
2024-03-24 16:38 ` dpdklab
2024-03-24 17:14 ` 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=202403221303.42MD3ORN1732272@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).