From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126849 [PATCH v4] net/iavf: add devargs to control watchdog
Date: Tue, 16 May 2023 09:33:32 +0800 [thread overview]
Message-ID: <202305160133.34G1XWI8105328@localhost.localdomain> (raw)
In-Reply-To: <20230515065405.795497-1-zhichaox.zeng@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126849
_Compilation OK_
Submitter: Zhichao Zeng <zhichaox.zeng@intel.com>
Date: Mon, 15 May 2023 14:54:05 +0800
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 1592a28c517d6dccbcee8e812f538808ccd5f3a7
126849 --> 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 prev parent reply other threads:[~2023-05-16 1:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230515065405.795497-1-zhichaox.zeng@intel.com>
2023-05-15 6:49 ` checkpatch
2023-05-15 8:00 ` 0-day Robot
2023-05-16 1:33 ` qemudev [this message]
2023-05-16 1:34 ` qemudev
2023-05-15 17:16 |SUCCESS| pw126849 [PATCH] [v4] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-05-15 9:35 dpdklab
2023-05-15 9:23 dpdklab
2023-05-15 9:18 dpdklab
2023-05-15 9:12 dpdklab
2023-05-15 9:11 dpdklab
2023-05-15 9:11 dpdklab
2023-05-15 9:03 dpdklab
2023-05-15 9:00 dpdklab
2023-05-15 8:59 dpdklab
2023-05-15 8:55 dpdklab
2023-05-15 8:54 dpdklab
2023-05-15 8:48 dpdklab
2023-05-15 8:43 dpdklab
2023-05-15 8:40 dpdklab
2023-05-15 8:38 dpdklab
2023-05-15 8:37 dpdklab
2023-05-15 8:37 dpdklab
2023-05-15 8:34 dpdklab
2023-05-15 8:26 dpdklab
2023-05-15 8:25 dpdklab
2023-05-15 8:20 dpdklab
2023-05-15 8:19 dpdklab
2023-05-15 8:18 dpdklab
2023-05-15 8:18 dpdklab
2023-05-15 8:18 dpdklab
2023-05-15 8:17 dpdklab
2023-05-15 8:12 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=202305160133.34G1XWI8105328@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).