automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124595-124596 [PATCH v3 2/2] app/testpmd: add support for bonding port's LACP negotiation
Date: Wed, 1 Mar 2023 16:08:32 +0800	[thread overview]
Message-ID: <202303010808.32188WhA951361@localhost.localdomain> (raw)
In-Reply-To: <20230301024826.885727-3-chaoyong.he@corigine.com>

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

_Compilation OK_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Wed,  1 Mar 2023 10:48:25 +0800
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 4ff773385cdbd525c6e5a10015894fa26c286760

124595-124596 --> 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:[~2023-03-01  8:22 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230301024826.885727-3-chaoyong.he@corigine.com>
2023-03-01  2:50 ` |SUCCESS| pw124596 " checkpatch
2023-03-01  4:39 ` 0-day Robot
2023-03-01  8:08 ` qemudev [this message]
2023-03-01  8:09 ` |SUCCESS| pw124595-124596 " qemudev
2023-03-01  3:34 |SUCCESS| pw124595-124596 [PATCH] [v3, " dpdklab
2023-03-01  3:41 dpdklab
2023-03-01  3:43 dpdklab
2023-03-01  3:46 dpdklab
2023-03-01  3:47 dpdklab
2023-03-01  3:49 dpdklab
2023-03-01  3:51 dpdklab
2023-03-01  3:51 dpdklab
2023-03-01  4:00 dpdklab
2023-03-01  4:02 dpdklab
2023-03-01  4:02 dpdklab
2023-03-01  4:06 dpdklab
2023-03-01  4:08 dpdklab
2023-03-01  4:09 dpdklab
2023-03-01  4:10 dpdklab
2023-03-01  4:20 dpdklab
2023-03-01  4:28 dpdklab
2023-03-01  4:40 dpdklab
2023-03-01  7:22 dpdklab
2023-03-01  7:35 dpdklab
2023-03-01  7:51 dpdklab
2023-03-01  8:03 dpdklab
2023-03-01  8:49 dpdklab
2023-03-01  9:02 dpdklab
2023-03-01  9:22 dpdklab
2023-03-01  9:34 dpdklab
2023-03-01 10:17 dpdklab
2023-03-01 10:38 dpdklab
2023-03-01 11:19 dpdklab
2023-03-01 11:42 dpdklab
2023-03-01 22:09 dpdklab
2023-03-01 22:31 dpdklab
2023-03-01 22:31 dpdklab
2023-03-01 22:35 dpdklab
2023-03-01 22:38 dpdklab
2023-03-01 22:39 dpdklab
2023-03-01 22:40 dpdklab
2023-03-01 22:42 dpdklab
2023-03-01 22:43 dpdklab
2023-03-01 22:56 dpdklab
2023-03-01 23:00 dpdklab
2023-03-01 23:55 dpdklab
2023-03-02  0:03 dpdklab
2023-03-02  0:04 dpdklab
2023-03-02  0:05 dpdklab
2023-03-02  0:06 dpdklab
2023-03-02  0:07 dpdklab
2023-03-02  0:23 dpdklab
2023-03-02  0:25 dpdklab
2023-03-02  0:26 dpdklab
2023-03-02  0:32 dpdklab
2023-03-02  0:34 dpdklab
2023-03-02  0:36 dpdklab
2023-03-02  0:37 dpdklab
2023-03-02  0:41 dpdklab
2023-03-02  1:42 dpdklab
2023-03-02  1:42 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=202303010808.32188WhA951361@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).