From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw136218 [PATCH] net/ixgbe: increase vf reset timeout
Date: Tue, 30 Jan 2024 17:38:08 +0800 [thread overview]
Message-ID: <202401300938.40U9c8Px565325@localhost.localdomain> (raw)
In-Reply-To: <20240130100027.39466-1-ktraynor@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/136218
_Compilation OK_
Submitter: Kevin Traynor <ktraynor@redhat.com>
Date: Tue, 30 Jan 2024 10:00:27 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 4e7732d6c4c64514dc26c3cc0203d19851b5f5aa
136218 --> 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:[~2024-01-30 10:02 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240130100027.39466-1-ktraynor@redhat.com>
2024-01-30 9:38 ` qemudev [this message]
2024-01-30 9:42 ` qemudev
2024-01-30 10:01 ` checkpatch
2024-01-30 11:03 ` 0-day Robot
2024-01-30 12:00 dpdklab
2024-01-30 12:00 dpdklab
2024-01-30 12:09 dpdklab
2024-01-30 12:12 dpdklab
2024-01-30 12:12 dpdklab
2024-01-30 12:13 dpdklab
2024-01-30 12:13 dpdklab
2024-01-30 12:14 dpdklab
2024-01-30 12:14 dpdklab
2024-01-30 12:14 dpdklab
2024-01-30 12:15 dpdklab
2024-01-30 12:16 dpdklab
2024-01-30 12:16 dpdklab
2024-01-30 12:17 dpdklab
2024-01-30 12:17 dpdklab
2024-01-30 12:17 dpdklab
2024-01-30 12:18 dpdklab
2024-01-30 12:18 dpdklab
2024-01-30 12:18 dpdklab
2024-01-30 12:19 dpdklab
2024-01-30 12:19 dpdklab
2024-01-30 12:19 dpdklab
2024-01-30 12:20 dpdklab
2024-01-30 12:20 dpdklab
2024-01-30 12:20 dpdklab
2024-01-30 12:21 dpdklab
2024-01-30 12:21 dpdklab
2024-01-30 12:21 dpdklab
2024-01-30 12:22 dpdklab
2024-01-30 12:23 dpdklab
2024-01-30 12:24 dpdklab
2024-01-30 12:24 dpdklab
2024-01-30 12:25 dpdklab
2024-01-30 12:25 dpdklab
2024-01-30 12:25 dpdklab
2024-01-30 12:27 dpdklab
2024-01-30 12:27 dpdklab
2024-01-30 12:28 dpdklab
2024-01-30 12:29 dpdklab
2024-01-30 12:29 dpdklab
2024-01-30 12:30 dpdklab
2024-01-30 12:31 dpdklab
2024-01-30 12:32 dpdklab
2024-01-30 12:33 dpdklab
2024-01-30 12:34 dpdklab
2024-01-30 12:34 dpdklab
2024-01-30 12:34 dpdklab
2024-01-30 12:35 dpdklab
2024-01-30 12:36 dpdklab
2024-01-30 12:37 dpdklab
2024-01-30 12:44 dpdklab
2024-01-30 12:46 dpdklab
2024-01-30 12:59 dpdklab
2024-01-30 13:07 dpdklab
2024-01-30 13:39 dpdklab
2024-01-30 13:48 dpdklab
2024-01-30 13:54 dpdklab
2024-01-30 14:10 dpdklab
2024-01-30 14:16 dpdklab
2024-01-30 14:17 dpdklab
2024-01-30 14:19 dpdklab
2024-01-30 14:45 dpdklab
2024-01-30 14:48 dpdklab
2024-01-30 14:51 dpdklab
2024-01-30 14:59 dpdklab
2024-01-30 15:02 dpdklab
2024-01-30 15:08 dpdklab
2024-01-30 15:09 dpdklab
2024-01-30 15:48 dpdklab
2024-01-30 16:23 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=202401300938.40U9c8Px565325@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).