automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw148926 [PATCH v1 1/1] net/ixgbe: fix missing VF PCI ID
Date: Fri, 29 Nov 2024 15:59:02 +0800	[thread overview]
Message-ID: <202411290759.4AT7x2HO3508242@localhost.localdomain> (raw)
In-Reply-To: <1c7487d2a77697d9edf1627f40fe539994714fc6.1732724174.git.anatoly.burakov@intel.com>

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

_Compilation OK_

Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Wed, 27 Nov 2024 16:16:17 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: main
  CommitID: 82eeeb9139f512c6b4a2599850119cccb74a666a

148926 --> 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


  parent reply	other threads:[~2024-11-29 12:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1c7487d2a77697d9edf1627f40fe539994714fc6.1732724174.git.anatoly.burakov@intel.com>
2024-11-27 16:16 ` checkpatch
2024-11-27 20:54 ` |SUCCESS| pw148926 [PATCH] [v1,1/1] " dpdklab
2024-11-27 20:55 ` |PENDING| " dpdklab
2024-11-27 21:01 ` |SUCCESS| " dpdklab
2024-11-27 21:06 ` dpdklab
2024-11-27 21:13 ` |PENDING| " dpdklab
2024-11-27 21:16 ` dpdklab
2024-11-27 21:28 ` |SUCCESS| " dpdklab
2024-11-27 21:36 ` |WARNING| " dpdklab
2024-11-27 21:36 ` dpdklab
2024-11-27 21:46 ` |SUCCESS| " dpdklab
2024-11-27 22:48 ` dpdklab
2024-11-27 22:55 ` dpdklab
2024-11-27 23:20 ` dpdklab
2024-11-27 23:28 ` dpdklab
2024-11-27 23:48 ` dpdklab
2024-11-27 23:52 ` dpdklab
2024-11-29  7:59 ` qemudev [this message]
2024-11-29  7:59 ` |SUCCESS| pw148926 [PATCH v1 1/1] " qemudev
2024-11-29 10:15 ` qemudev
2024-11-29 10:16 ` qemudev

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=202411290759.4AT7x2HO3508242@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).