automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw120534 [PATCH v3] net/memif: change socket listener owner uid/gid
Date: Fri, 9 Dec 2022 00:09:57 +0800	[thread overview]
Message-ID: <202212081609.2B8G9vOI194630@localhost.localdomain> (raw)
In-Reply-To: <c07a6be6e25d7343@cs.arizona.edu>

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

_Compilation OK_

Submitter: Junxiao Shi <git@mail1.yoursunny.com>
Date: Wed, 7 Dec 2022 15:53:27 +0000
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 6f59b7f0082ab8ffa79e87b1625279903b74ab05

120534 --> 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:[~2022-12-12 11:35 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c07a6be6e25d7343@cs.arizona.edu>
2022-12-07 17:50 ` checkpatch
2022-12-07 19:18 ` 0-day Robot
2022-12-08 16:09 ` qemudev [this message]
2022-12-08 16:10 ` qemudev
2022-12-08 16:45 ` qemudev
2022-12-08 16:46 ` qemudev
2022-12-09  4:06 ` qemudev
2022-12-09  4:07 ` qemudev
2022-12-10  0:34 ` qemudev
2022-12-10  0:35 ` qemudev
2022-12-07 22:07 |SUCCESS| pw120534 [PATCH] [v3] " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2022-12-07 21:29 dpdklab
2022-12-07 21:29 dpdklab
2022-12-07 21:29 dpdklab
2022-12-07 21:29 dpdklab
2022-12-07 21:28 dpdklab
2022-12-07 21:03 dpdklab
2022-12-07 21:03 dpdklab
2022-12-07 21:03 dpdklab
2022-12-07 20:24 dpdklab
2022-12-07 19:31 dpdklab
2022-12-07 18:41 dpdklab
2022-12-07 18:37 dpdklab
2022-12-07 18:34 dpdklab
2022-12-07 18:30 dpdklab
2022-12-07 18:28 dpdklab
2022-12-07 18:22 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=202212081609.2B8G9vOI194630@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).