automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121359 [PATCH] net/vmxnet3: added checks for TCP for RSS Configuration
Date: Sat, 24 Dec 2022 17:54:46 +0800	[thread overview]
Message-ID: <202212240954.2BO9sk5n3175705@localhost.localdomain> (raw)
In-Reply-To: <20221222082434.18336-1-royra@vmware.com>

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

_Compilation OK_

Submitter: Raghav Roy <royra@vmware.com>
Date: Thu, 22 Dec 2022 00:24:34 -0800
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 9351bc0906b4585fd9d50a89f9f6d2f091d3e822

121359 --> 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:[~2022-12-24 10:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221222082434.18336-1-royra@vmware.com>
2022-12-24  9:54 ` qemudev [this message]
2022-12-24  9:58 ` |FAILURE| " qemudev
2022-12-24 10:03 ` |WARNING| " checkpatch
2022-12-27  0:57 ` |SUCCESS| " qemudev
2022-12-27  1:01 ` qemudev
2022-12-27  2:00 ` qemudev
2022-12-27  2:04 ` qemudev
2022-12-24 13:51 dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2022-12-24 13:51 dpdklab
2022-12-24 13:50 dpdklab
2022-12-24 13:47 dpdklab
2022-12-24 13:18 dpdklab
2022-12-24 13:18 dpdklab
2022-12-24 13:18 dpdklab
2022-12-24 13:18 dpdklab
2022-12-24 13:17 dpdklab
2022-12-24 13:15 dpdklab
2022-12-24 12:22 dpdklab
2022-12-24 12:14 dpdklab
2022-12-24 11:34 dpdklab
2022-12-24 11:12 dpdklab
2022-12-24 10:49 dpdklab
2022-12-24 10:45 dpdklab
2022-12-24 10:42 dpdklab
2022-12-24 10:38 dpdklab
2022-12-24 10:34 dpdklab
2022-12-24 10:30 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=202212240954.2BO9sk5n3175705@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).