automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125957-125959 [PATCH v2 3/3] net/iavf: support Rx timestamp offload on SSE
Date: Wed, 12 Apr 2023 16:32:12 +0800	[thread overview]
Message-ID: <202304120832.33C8WCxq993378@localhost.localdomain> (raw)
In-Reply-To: <20230412084657.3622484-1-zhichaox.zeng@intel.com>

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

_Compilation OK_

Submitter: Zhichao Zeng <zhichaox.zeng@intel.com>
Date: Wed, 12 Apr 2023 16:46:04 +0800
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: main
  CommitID: 3bc3d9f9f3df2e22c3958d1a3dac68ce2d708b33

125957-125959 --> 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-04-12  8:46 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230412084657.3622484-1-zhichaox.zeng@intel.com>
2023-04-12  8:32 ` qemudev [this message]
2023-04-12  8:36 ` qemudev
2023-04-12  8:42 ` |WARNING| pw125959 " checkpatch
2023-04-12  9:58 ` |SUCCESS| " 0-day Robot
2023-04-12  9:19 |SUCCESS| pw125957-125959 [PATCH] [v2, " dpdklab
2023-04-12  9:26 dpdklab
2023-04-12  9:26 dpdklab
2023-04-12  9:30 dpdklab
2023-04-12  9:30 dpdklab
2023-04-12  9:33 dpdklab
2023-04-12  9:34 dpdklab
2023-04-12  9:39 dpdklab
2023-04-12  9:40 dpdklab
2023-04-12  9:44 dpdklab
2023-04-12  9:46 dpdklab
2023-04-12  9:47 dpdklab
2023-04-12  9:48 dpdklab
2023-04-12  9:49 dpdklab
2023-04-12  9:49 dpdklab
2023-04-12  9:50 dpdklab
2023-04-12  9:55 dpdklab
2023-04-12  9:59 dpdklab
2023-04-12 10:01 dpdklab
2023-04-12 10:03 dpdklab
2023-04-12 10:06 dpdklab
2023-04-12 10:06 dpdklab
2023-04-12 10:11 dpdklab
2023-04-12 10:11 dpdklab
2023-04-12 10:16 dpdklab
2023-04-12 10:24 dpdklab
2023-04-12 10:38 dpdklab
2023-04-12 10:38 dpdklab
2023-04-12 17:57 dpdklab
2023-04-12 18:12 dpdklab
2023-04-12 18:17 dpdklab
2023-04-12 18:22 dpdklab
2023-04-12 18:38 dpdklab
2023-04-12 18:43 dpdklab
2023-04-12 19:11 dpdklab
2023-04-12 19:13 dpdklab
2023-04-12 19:13 dpdklab
2023-04-12 19:17 dpdklab
2023-04-12 19:18 dpdklab
2023-04-12 19:22 dpdklab
2023-04-12 19:28 dpdklab
2023-04-12 19:31 dpdklab
2023-04-12 20:53 dpdklab
2023-04-12 20:57 dpdklab
2023-04-12 20:59 dpdklab
2023-04-12 21:03 dpdklab
2023-04-12 21:09 dpdklab
2023-04-12 21:11 dpdklab
2023-04-12 21:13 dpdklab
2023-04-12 21:20 dpdklab
2023-04-12 21:24 dpdklab
2023-04-12 21:32 dpdklab
2023-04-12 21:40 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=202304120832.33C8WCxq993378@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).