automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121538 [PATCH] vhost: fix net header settings in vhost datapath
Date: Wed, 4 Jan 2023 11:16:55 +0800	[thread overview]
Message-ID: <202301040316.3043GtIl2520253@localhost.localdomain> (raw)
In-Reply-To: <20230104023945.6669-1-wenwux.ma@intel.com>

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

_Compilation OK_

Submitter: Wenwu Ma <wenwux.ma@intel.com>
Date: Wed,  4 Jan 2023 10:39:45 +0800
DPDK git baseline: Repo:dpdk-next-virtio
  Branch: main
  CommitID: f262f16087ea6a77357a915cf4c0d10ddc7b6562

121538 --> 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:[~2023-01-04  3:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230104023945.6669-1-wenwux.ma@intel.com>
2023-01-04  2:43 ` checkpatch
2023-01-04  3:16 ` qemudev [this message]
2023-01-04  3:20 ` qemudev
2023-01-04  3:39 ` 0-day Robot
2023-01-04 11:35 dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-01-04  8:58 dpdklab
2023-01-04  8:48 dpdklab
2023-01-04  5:50 dpdklab
2023-01-04  5:50 dpdklab
2023-01-04  5:49 dpdklab
2023-01-04  5:49 dpdklab
2023-01-04  5:48 dpdklab
2023-01-04  5:48 dpdklab
2023-01-04  5:42 dpdklab
2023-01-04  5:41 dpdklab
2023-01-04  5:41 dpdklab
2023-01-04  5:35 dpdklab
2023-01-04  5:03 dpdklab
2023-01-04  4:42 dpdklab
2023-01-04  3:30 dpdklab
2023-01-04  3:26 dpdklab
2023-01-04  3:22 dpdklab
2023-01-04  3:15 dpdklab
2023-01-04  3:10 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=202301040316.3043GtIl2520253@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).