automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw134608 [PATCH v2] doc: update release notes for 23.11
Date: Fri, 24 Nov 2023 23:01:32 +0800	[thread overview]
Message-ID: <202311241501.3AOF1WcT810744@localhost.localdomain> (raw)
In-Reply-To: <20231124152028.3892722-1-john.mcnamara@intel.com>

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

_Compilation OK_

Submitter: John McNamara <john.mcnamara@intel.com>
Date: Fri, 24 Nov 2023 15:20:28 +0000
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 4358da71b382d1015be7323e1b48d15e34f2562b

134608 --> 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-24 15:22 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231124152028.3892722-1-john.mcnamara@intel.com>
2023-11-24 15:01 ` qemudev [this message]
2023-11-24 15:05 ` qemudev
2023-11-24 15:21 ` checkpatch
2023-11-24 16:16 ` 0-day Robot
2023-11-24 15:57 |SUCCESS| pw134608 [PATCH] [v2] " dpdklab
2023-11-24 15:57 dpdklab
2023-11-24 15:57 dpdklab
2023-11-24 15:57 dpdklab
2023-11-24 15:58 dpdklab
2023-11-24 15:58 dpdklab
2023-11-24 15:58 dpdklab
2023-11-24 15:58 dpdklab
2023-11-24 15:58 dpdklab
2023-11-24 15:58 dpdklab
2023-11-24 15:58 dpdklab
2023-11-24 15:58 dpdklab
2023-11-24 15:59 dpdklab
2023-11-24 15:59 dpdklab
2023-11-24 15:59 dpdklab
2023-11-24 15:59 dpdklab
2023-11-24 16:00 dpdklab
2023-11-24 16:00 dpdklab
2023-11-24 16:01 dpdklab
2023-11-24 16:01 dpdklab
2023-11-24 16:02 dpdklab
2023-11-24 16:02 dpdklab
2023-11-24 16:03 dpdklab
2023-11-24 16:03 dpdklab
2023-11-24 16:03 dpdklab
2023-11-24 16:03 dpdklab
2023-11-24 16:03 dpdklab
2023-11-24 16:04 dpdklab
2023-11-24 16:05 dpdklab
2023-11-24 16:06 dpdklab
2023-11-24 16:07 dpdklab
2023-11-24 16:07 dpdklab
2023-11-24 16:08 dpdklab
2023-11-24 16:09 dpdklab
2023-11-24 16:09 dpdklab
2023-11-24 16:09 dpdklab
2023-11-24 16:10 dpdklab
2023-11-24 16:12 dpdklab
2023-11-24 16:12 dpdklab
2023-11-24 16:12 dpdklab
2023-11-24 16:14 dpdklab
2023-11-24 16:15 dpdklab
2023-11-24 16:16 dpdklab
2023-11-24 16:17 dpdklab
2023-11-24 16:18 dpdklab
2023-11-24 16:20 dpdklab
2023-11-24 16:27 dpdklab
2023-11-24 16:28 dpdklab
2023-11-24 16:51 dpdklab
2023-11-24 18:44 dpdklab
2023-11-27 18:53 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=202311241501.3AOF1WcT810744@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).