automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw130662 [PATCH v2] net/iavf: fix checksum offloading
Date: Wed, 23 Aug 2023 14:17:02 +0800	[thread overview]
Message-ID: <202308230617.37N6H2aT2005562@localhost.localdomain> (raw)
In-Reply-To: <20230823062911.2483926-1-david.marchand@redhat.com>

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

_Compilation OK_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Wed, 23 Aug 2023 08:29:11 +0200
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: main
  CommitID: ed787f9b9b08e336c269aeb01bba73b1888716c1

130662 --> 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-08-23  6:31 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230823062911.2483926-1-david.marchand@redhat.com>
2023-08-23  6:17 ` qemudev [this message]
2023-08-23  6:21 ` qemudev
2023-08-23  6:30 ` checkpatch
2023-08-23  7:19 ` 0-day Robot
2023-08-23 11:19 |SUCCESS| pw130662 [PATCH] [v2] " dpdklab
2023-08-23 11:31 dpdklab
2023-08-23 11:32 dpdklab
2023-08-23 11:33 dpdklab
2023-08-23 11:35 dpdklab
2023-08-23 11:35 dpdklab
2023-08-23 11:36 dpdklab
2023-08-23 11:36 dpdklab
2023-08-23 11:36 dpdklab
2023-08-23 11:37 dpdklab
2023-08-23 11:37 dpdklab
2023-08-23 11:37 dpdklab
2023-08-23 11:37 dpdklab
2023-08-23 11:37 dpdklab
2023-08-23 11:37 dpdklab
2023-08-23 11:39 dpdklab
2023-08-23 11:39 dpdklab
2023-08-23 11:40 dpdklab
2023-08-23 11:40 dpdklab
2023-08-23 11:40 dpdklab
2023-08-23 11:40 dpdklab
2023-08-23 11:40 dpdklab
2023-08-23 11:41 dpdklab
2023-08-23 11:41 dpdklab
2023-08-23 11:41 dpdklab
2023-08-23 11:41 dpdklab
2023-08-23 11:42 dpdklab
2023-08-23 11:45 dpdklab
2023-08-23 11:51 dpdklab
2023-08-23 11:51 dpdklab
2023-08-23 11:51 dpdklab
2023-08-23 11:51 dpdklab
2023-08-23 11:52 dpdklab
2023-08-23 11:53 dpdklab
2023-08-23 11:54 dpdklab
2023-08-23 11:55 dpdklab
2023-08-23 11:56 dpdklab
2023-08-23 11:56 dpdklab
2023-08-23 11:57 dpdklab
2023-08-23 11:59 dpdklab
2023-08-23 12:47 dpdklab
2023-08-23 13:15 dpdklab
2023-08-23 13:35 dpdklab
2023-08-24  0:29 dpdklab
2023-08-24  0:34 dpdklab
2023-08-24  0:38 dpdklab
2023-08-24  0:59 dpdklab
2023-08-24  1:24 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=202308230617.37N6H2aT2005562@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).