automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138872 [PATCH] net/ice: fix vlan stripping in double VLAN mode
Date: Thu, 28 Mar 2024 02:28:22 +0800	[thread overview]
Message-ID: <202403271828.42RISMKs3716111@localhost.localdomain> (raw)
In-Reply-To: <20240327184413.3192526-1-vladimir.medvedkin@intel.com>

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

_Compilation OK_

Submitter: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Date: Wed, 27 Mar 2024 18:44:13 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: main
  CommitID: 2c54ea7a59dfc0a819d3527309c62846fc8853af

138872 --> 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-27 18:53 UTC|newest]

Thread overview: 91+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240327184413.3192526-1-vladimir.medvedkin@intel.com>
2024-03-27 18:28 ` qemudev [this message]
2024-03-27 18:32 ` qemudev
2024-03-27 18:45 ` checkpatch
2024-03-27 19:21 ` |SUCCESS| pw138872 [PATCH] net/ice: fix vlan stripping in double VLA dpdklab
2024-03-27 19:22 ` dpdklab
2024-03-27 19:22 ` dpdklab
2024-03-27 19:23 ` dpdklab
2024-03-27 19:23 ` dpdklab
2024-03-27 19:23 ` dpdklab
2024-03-27 19:24 ` dpdklab
2024-03-27 19:24 ` dpdklab
2024-03-27 19:24 ` dpdklab
2024-03-27 19:24 ` dpdklab
2024-03-27 19:25 ` dpdklab
2024-03-27 19:25 ` dpdklab
2024-03-27 19:25 ` dpdklab
2024-03-27 19:25 ` dpdklab
2024-03-27 19:25 ` dpdklab
2024-03-27 19:26 ` dpdklab
2024-03-27 19:26 ` dpdklab
2024-03-27 19:26 ` dpdklab
2024-03-27 19:27 ` dpdklab
2024-03-27 19:27 ` dpdklab
2024-03-27 19:27 ` dpdklab
2024-03-27 19:28 ` dpdklab
2024-03-27 19:28 ` dpdklab
2024-03-27 19:28 ` dpdklab
2024-03-27 19:29 ` dpdklab
2024-03-27 19:30 ` dpdklab
2024-03-27 19:30 ` dpdklab
2024-03-27 19:30 ` dpdklab
2024-03-27 19:30 ` dpdklab
2024-03-27 19:31 ` dpdklab
2024-03-27 19:32 ` dpdklab
2024-03-27 19:33 ` dpdklab
2024-03-27 19:33 ` dpdklab
2024-03-27 19:33 ` dpdklab
2024-03-27 19:34 ` dpdklab
2024-03-27 19:35 ` dpdklab
2024-03-27 19:35 ` dpdklab
2024-03-27 19:35 ` dpdklab
2024-03-27 19:35 ` dpdklab
2024-03-27 19:36 ` dpdklab
2024-03-27 19:37 ` dpdklab
2024-03-27 19:37 ` dpdklab
2024-03-27 19:38 ` dpdklab
2024-03-27 19:39 ` dpdklab
2024-03-27 19:39 ` dpdklab
2024-03-27 19:39 ` dpdklab
2024-03-27 19:39 ` dpdklab
2024-03-27 19:40 ` dpdklab
2024-03-27 19:40 ` dpdklab
2024-03-27 19:41 ` dpdklab
2024-03-27 19:41 ` dpdklab
2024-03-27 19:41 ` dpdklab
2024-03-27 19:42 ` dpdklab
2024-03-27 19:43 ` dpdklab
2024-03-27 19:44 ` dpdklab
2024-03-27 19:45 ` |SUCCESS| pw138872 [PATCH] net/ice: fix vlan stripping in double VLAN mode 0-day Robot
2024-03-27 19:45 ` |SUCCESS| pw138872 [PATCH] net/ice: fix vlan stripping in double VLA dpdklab
2024-03-27 19:45 ` dpdklab
2024-03-27 19:45 ` dpdklab
2024-03-27 19:46 ` dpdklab
2024-03-27 19:47 ` dpdklab
2024-03-27 19:48 ` dpdklab
2024-03-27 19:49 ` dpdklab
2024-03-27 19:49 ` dpdklab
2024-03-27 19:49 ` dpdklab
2024-03-27 19:53 ` dpdklab
2024-03-27 19:53 ` dpdklab
2024-03-27 19:53 ` dpdklab
2024-03-27 19:54 ` dpdklab
2024-03-27 19:55 ` dpdklab
2024-03-27 19:58 ` dpdklab
2024-03-27 20:01 ` dpdklab
2024-03-27 20:03 ` dpdklab
2024-03-27 20:04 ` dpdklab
2024-03-27 20:05 ` dpdklab
2024-03-27 20:08 ` dpdklab
2024-03-27 20:08 ` dpdklab
2024-03-27 20:13 ` dpdklab
2024-03-27 20:24 ` dpdklab
2024-03-27 20:34 ` dpdklab
2024-03-27 20:35 ` dpdklab
2024-03-27 20:48 ` dpdklab
2024-03-27 22:17 ` dpdklab
2024-04-02 10:42 ` dpdklab
2024-04-02 10:47 ` dpdklab
2024-04-02 10:50 ` dpdklab
2024-04-02 11:10 ` dpdklab
2024-04-02 11:14 ` 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=202403271828.42RISMKs3716111@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).