From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124069 [PATCH] net/virtio: deduce IP length for Virtio TSO checksum
Date: Thu, 16 Feb 2023 20:24:33 +0800 [thread overview]
Message-ID: <202302161224.31GCOXnx1412229@localhost.localdomain> (raw)
In-Reply-To: <20230216123554.2628837-2-boleslav.stankevich@oktetlabs.ru>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124069
_Compilation OK_
Submitter: Boleslav Stankevich <boleslav.stankevich@oktetlabs.ru>
Date: Thu, 16 Feb 2023 15:35:54 +0300
DPDK git baseline: Repo:dpdk-next-virtio
Branch: main
CommitID: fe2c18a0a8b22703dec3add385a371ad819d7872
124069 --> 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
next parent reply other threads:[~2023-02-16 12:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230216123554.2628837-2-boleslav.stankevich@oktetlabs.ru>
2023-02-16 12:24 ` qemudev [this message]
2023-02-16 12:28 ` qemudev
2023-02-16 12:37 ` |WARNING| " checkpatch
2023-02-16 15:20 ` |SUCCESS| " 0-day Robot
2023-02-16 13:08 dpdklab
2023-02-16 13:09 dpdklab
2023-02-16 13:13 dpdklab
2023-02-16 13:14 dpdklab
2023-02-16 13:21 dpdklab
2023-02-16 15:31 dpdklab
2023-02-16 15:47 dpdklab
2023-02-16 15:52 dpdklab
2023-02-16 15:54 dpdklab
2023-02-16 15:55 dpdklab
2023-02-16 15:59 dpdklab
2023-02-16 15:59 dpdklab
2023-02-16 16:02 dpdklab
2023-02-16 16:03 dpdklab
2023-02-16 16:07 dpdklab
2023-02-16 16:10 dpdklab
2023-02-16 16:13 dpdklab
2023-02-16 16:22 dpdklab
2023-02-16 16:22 dpdklab
2023-02-17 21:47 dpdklab
2023-02-19 9:35 dpdklab
2023-02-24 23:09 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=202302161224.31GCOXnx1412229@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).