automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw133870 [PATCH] examples/l3fwd: fix missing unlock issue
Date: Sat, 4 Nov 2023 15:10:47 +0800	[thread overview]
Message-ID: <202311040710.3A47AlZf078260@localhost.localdomain> (raw)
In-Reply-To: <tencent_221F3CE2A7B111333A16DF62235322503108@qq.com>

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

_Compilation OK_

Submitter: Weiguo Li <liwg06@foxmail.com>
Date: Sat,  4 Nov 2023 15:27:37 +0800
DPDK git baseline: Repo:dpdk-next-eventdev
  Branch: for-main
  CommitID: af7930610251844109797a6b2f33f8d37ef4aa39

133870 --> 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-11-04  7:31 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tencent_221F3CE2A7B111333A16DF62235322503108@qq.com>
2023-11-04  7:10 ` qemudev [this message]
2023-11-04  7:14 ` qemudev
2023-11-04  7:28 ` |WARNING| " checkpatch
2023-11-04  9:10 |SUCCESS| " dpdklab
2023-11-04  9:12 dpdklab
2023-11-04  9:14 dpdklab
2023-11-04  9:14 dpdklab
2023-11-04  9:16 dpdklab
2023-11-04  9:16 dpdklab
2023-11-04  9:17 dpdklab
2023-11-04  9:17 dpdklab
2023-11-04  9:31 dpdklab
2023-11-04  9:41 dpdklab
2023-11-04  9:43 dpdklab
2023-11-04  9:43 dpdklab
2023-11-04  9:43 dpdklab
2023-11-04  9:43 dpdklab
2023-11-04  9:43 dpdklab
2023-11-04  9:43 dpdklab
2023-11-04  9:43 dpdklab
2023-11-04  9:43 dpdklab
2023-11-04  9:44 dpdklab
2023-11-04  9:44 dpdklab
2023-11-04  9:45 dpdklab
2023-11-04  9:45 dpdklab
2023-11-04  9:54 dpdklab
2023-11-04  9:55 dpdklab
2023-11-04  9:55 dpdklab
2023-11-04  9:55 dpdklab
2023-11-04  9:55 dpdklab
2023-11-04  9:56 dpdklab
2023-11-04 10:02 dpdklab
2023-11-04 10:02 dpdklab
2023-11-04 10:03 dpdklab
2023-11-04 10:03 dpdklab
2023-11-04 10:03 dpdklab
2023-11-04 10:04 dpdklab
2023-11-04 10:04 dpdklab
2023-11-04 10:04 dpdklab
2023-11-04 10:04 dpdklab
2023-11-04 10:04 dpdklab
2023-11-04 10:05 dpdklab
2023-11-04 10:05 dpdklab
2023-11-04 10:05 dpdklab
2023-11-04 10:05 dpdklab
2023-11-04 10:06 dpdklab
2023-11-04 10:06 dpdklab
2023-11-04 10:07 dpdklab
2023-11-04 10:07 dpdklab
2023-11-04 10:07 dpdklab
2023-11-04 10:08 dpdklab
2023-11-04 10:11 dpdklab
2023-11-04 11:09 dpdklab
2023-11-04 12:21 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=202311040710.3A47AlZf078260@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).