automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw132606 [PATCH] net/iavf: fix pkt len check
Date: Fri, 13 Oct 2023 19:22:51 +0800	[thread overview]
Message-ID: <202310131122.39DBMpd1589258@localhost.localdomain> (raw)
In-Reply-To: <20231013114125.376-1-dexia.li@jaguarmicro.com>

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

_Compilation OK_

Submitter: Dexia Li <dexia.li@jaguarmicro.com>
Date: Fri, 13 Oct 2023 19:41:25 +0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 77f913752a55c0262bfda99a1b69ca0bd804c6c7

132606 --> 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-10-13 11:43 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231013114125.376-1-dexia.li@jaguarmicro.com>
2023-10-13 11:22 ` qemudev [this message]
2023-10-13 11:27 ` qemudev
2023-10-13 11:43 ` checkpatch
2023-10-13 13:31 ` 0-day Robot
2023-10-13 14:10 dpdklab
2023-10-13 14:10 dpdklab
2023-10-13 14:11 dpdklab
2023-10-13 14:11 dpdklab
2023-10-13 14:11 dpdklab
2023-10-13 14:12 dpdklab
2023-10-13 14:12 dpdklab
2023-10-13 14:12 dpdklab
2023-10-13 14:12 dpdklab
2023-10-13 14:13 dpdklab
2023-10-13 14:13 dpdklab
2023-10-13 14:13 dpdklab
2023-10-13 14:13 dpdklab
2023-10-13 14:14 dpdklab
2023-10-13 14:14 dpdklab
2023-10-13 14:14 dpdklab
2023-10-13 14:14 dpdklab
2023-10-13 14:14 dpdklab
2023-10-13 14:14 dpdklab
2023-10-13 14:15 dpdklab
2023-10-13 14:15 dpdklab
2023-10-13 14:15 dpdklab
2023-10-13 14:16 dpdklab
2023-10-13 14:16 dpdklab
2023-10-13 14:17 dpdklab
2023-10-13 14:19 dpdklab
2023-10-13 14:20 dpdklab
2023-10-13 14:22 dpdklab
2023-10-13 14:23 dpdklab
2023-10-13 14:24 dpdklab
2023-10-13 14:25 dpdklab
2023-10-13 14:31 dpdklab
2023-10-13 14:32 dpdklab
2023-10-13 14:32 dpdklab
2023-10-13 14:33 dpdklab
2023-10-13 14:36 dpdklab
2023-10-13 14:36 dpdklab
2023-10-13 14:39 dpdklab
2023-10-13 14:40 dpdklab
2023-10-13 14:43 dpdklab
2023-10-13 14:45 dpdklab
2023-10-13 14:45 dpdklab
2023-10-13 14:46 dpdklab
2023-10-13 14:47 dpdklab
2023-10-13 14:50 dpdklab
2023-10-13 14:55 dpdklab
2023-10-13 15:09 dpdklab
2023-10-13 15:30 dpdklab
2023-10-13 15:37 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=202310131122.39DBMpd1589258@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).