automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137983 [RFC] net/gve: add IPv4 checksum offloading capability
Date: Tue, 5 Mar 2024 16:16:50 +0800	[thread overview]
Message-ID: <202403050816.4258GoTF1566531@localhost.localdomain> (raw)
In-Reply-To: <20240305084026.2329691-1-rushilg@google.com>

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

_Compilation OK_

Submitter: Rushil Gupta <rushilg@google.com>
Date: Tue,  5 Mar 2024 08:40:26 +0000
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 29c516fa4f5bac381825667b5bdb1ced4548c6bc

137983 --> 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:[~2024-03-05  8:41 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240305084026.2329691-1-rushilg@google.com>
2024-03-05  8:16 ` qemudev [this message]
2024-03-05  8:21 ` qemudev
2024-03-05  8:41 ` |WARNING| " checkpatch
2024-03-05  9:45 ` |SUCCESS| " 0-day Robot
2024-03-05  9:46 ` |SUCCESS| pw137983 [PATCH] [RFC] net/gve: add IPv4 checksum offloadi dpdklab
2024-03-05  9:46 ` dpdklab
2024-03-05  9:47 ` dpdklab
2024-03-05  9:47 ` dpdklab
2024-03-05  9:52 ` dpdklab
2024-03-05  9:52 ` dpdklab
2024-03-05  9:53 ` dpdklab
2024-03-05  9:53 ` dpdklab
2024-03-05  9:54 ` dpdklab
2024-03-05  9:54 ` dpdklab
2024-03-05  9:54 ` dpdklab
2024-03-05  9:55 ` dpdklab
2024-03-05  9:55 ` dpdklab
2024-03-05  9:55 ` dpdklab
2024-03-05  9:55 ` dpdklab
2024-03-05  9:56 ` dpdklab
2024-03-05  9:56 ` dpdklab
2024-03-05  9:56 ` dpdklab
2024-03-05  9:56 ` dpdklab
2024-03-05  9:57 ` dpdklab
2024-03-05  9:57 ` dpdklab
2024-03-05  9:57 ` dpdklab
2024-03-05  9:58 ` dpdklab
2024-03-05  9:58 ` dpdklab
2024-03-05  9:58 ` dpdklab
2024-03-05  9:58 ` dpdklab
2024-03-05  9:58 ` dpdklab
2024-03-05  9:58 ` dpdklab
2024-03-05  9:59 ` dpdklab
2024-03-05  9:59 ` dpdklab
2024-03-05  9:59 ` dpdklab
2024-03-05  9:59 ` dpdklab
2024-03-05 10:00 ` dpdklab
2024-03-05 10:00 ` dpdklab
2024-03-05 10:00 ` dpdklab
2024-03-05 10:00 ` dpdklab
2024-03-05 10:01 ` dpdklab
2024-03-05 10:01 ` dpdklab
2024-03-05 10:01 ` dpdklab
2024-03-05 10:01 ` dpdklab
2024-03-05 10:01 ` dpdklab
2024-03-05 10:02 ` dpdklab
2024-03-05 10:02 ` dpdklab
2024-03-05 10:02 ` dpdklab
2024-03-05 10:02 ` dpdklab
2024-03-05 10:02 ` dpdklab
2024-03-05 10:03 ` dpdklab
2024-03-05 10:04 ` dpdklab
2024-03-05 10:05 ` dpdklab
2024-03-05 10:05 ` dpdklab
2024-03-05 10:06 ` dpdklab
2024-03-05 10:06 ` dpdklab
2024-03-05 10:06 ` dpdklab
2024-03-05 10:06 ` dpdklab
2024-03-05 10:07 ` dpdklab
2024-03-05 10:07 ` dpdklab
2024-03-05 10:07 ` dpdklab
2024-03-05 10:07 ` dpdklab
2024-03-05 10:08 ` dpdklab
2024-03-05 10:08 ` dpdklab
2024-03-05 10:08 ` dpdklab
2024-03-05 10:08 ` dpdklab
2024-03-05 10:09 ` dpdklab
2024-03-05 10:12 ` dpdklab
2024-03-05 10:13 ` dpdklab
2024-03-05 10:26 ` dpdklab
2024-03-05 10:26 ` dpdklab
2024-03-05 10:26 ` dpdklab
2024-03-05 11:10 ` dpdklab
2024-03-08 22:20 ` dpdklab
2024-03-08 22:57 ` dpdklab
2024-03-08 23:25 ` 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=202403050816.4258GoTF1566531@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).