From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121572 [PATCH] net/ixgbe: fix ixgbe firmware version get
Date: Wed, 4 Jan 2023 17:53:03 +0800 [thread overview]
Message-ID: <202301040953.3049r3cB3143001@localhost.localdomain> (raw)
In-Reply-To: <20230104095142.86796-1-shiyangx.he@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/121572
_Compilation OK_
Submitter: Shiyang He <shiyangx.he@intel.com>
Date: Wed, 4 Jan 2023 09:51:42 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 43d326b6f923f32473f550228910e1bd5de3f3fb
121572 --> 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-01-04 10:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230104095142.86796-1-shiyangx.he@intel.com>
2023-01-04 9:53 ` qemudev [this message]
2023-01-04 9:56 ` qemudev
2023-01-04 10:02 ` |WARNING| " checkpatch
2023-01-04 11:19 ` |SUCCESS| " 0-day Robot
2023-01-05 8:13 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-01-05 6:59 dpdklab
2023-01-05 5:09 dpdklab
2023-01-04 20:29 dpdklab
2023-01-04 20:29 dpdklab
2023-01-04 20:29 dpdklab
2023-01-04 20:29 dpdklab
2023-01-04 20:23 dpdklab
2023-01-04 20:18 dpdklab
2023-01-04 20:18 dpdklab
2023-01-04 20:18 dpdklab
2023-01-04 18:47 dpdklab
2023-01-04 13:39 dpdklab
2023-01-04 10:51 dpdklab
2023-01-04 10:46 dpdklab
2023-01-04 10:44 dpdklab
2023-01-04 10:39 dpdklab
2023-01-04 10:36 dpdklab
2023-01-04 10:31 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=202301040953.3049r3cB3143001@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).