From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw135882 [PATCH] maintainers: update for e1000/ixgbe
Date: Tue, 16 Jan 2024 14:11:08 +0800 [thread overview]
Message-ID: <202401160611.40G6B8Bx1223550@localhost.localdomain> (raw)
In-Reply-To: <20240116063326.951911-1-wenjun1.wu@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/135882
_Compilation OK_
Submitter: Wenjun Wu <wenjun1.wu@intel.com>
Date: Tue, 16 Jan 2024 14:33:26 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: d4af9a82063e4c39568191eaa12955d3ca39581a
135882 --> 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-16 6:35 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240116063326.951911-1-wenjun1.wu@intel.com>
2024-01-16 6:11 ` qemudev [this message]
2024-01-16 6:15 ` qemudev
2024-01-16 6:34 ` checkpatch
2024-01-16 7:24 ` 0-day Robot
2024-01-16 22:48 dpdklab
2024-01-16 22:49 dpdklab
2024-01-16 22:51 dpdklab
2024-01-16 22:53 dpdklab
2024-01-16 22:55 dpdklab
2024-01-16 23:14 dpdklab
2024-01-16 23:20 dpdklab
2024-01-16 23:24 dpdklab
2024-01-16 23:25 dpdklab
2024-01-16 23:27 dpdklab
2024-01-16 23:45 dpdklab
2024-01-16 23:47 dpdklab
2024-01-16 23:48 dpdklab
2024-01-16 23:49 dpdklab
2024-01-16 23:50 dpdklab
2024-01-16 23:52 dpdklab
2024-01-16 23:52 dpdklab
2024-01-17 1:11 dpdklab
2024-01-17 1:15 dpdklab
2024-01-17 1:18 dpdklab
2024-01-17 2:19 dpdklab
2024-01-17 2:19 dpdklab
2024-01-17 2:23 dpdklab
2024-01-17 2:27 dpdklab
2024-01-17 2:32 dpdklab
2024-01-17 2:32 dpdklab
2024-01-17 2:32 dpdklab
2024-01-17 2:32 dpdklab
2024-01-17 2:35 dpdklab
2024-01-17 2:35 dpdklab
2024-01-17 2:35 dpdklab
2024-01-17 2:35 dpdklab
2024-01-17 2:35 dpdklab
2024-01-17 2:35 dpdklab
2024-01-17 2:36 dpdklab
2024-01-17 2:36 dpdklab
2024-01-17 2:36 dpdklab
2024-01-17 2:36 dpdklab
2024-01-17 2:36 dpdklab
2024-01-17 2:37 dpdklab
2024-01-17 2:37 dpdklab
2024-01-17 2:37 dpdklab
2024-01-17 2:37 dpdklab
2024-01-17 2:37 dpdklab
2024-01-17 2:37 dpdklab
2024-01-17 2:37 dpdklab
2024-01-17 2:37 dpdklab
2024-01-17 2:38 dpdklab
2024-01-17 2:38 dpdklab
2024-01-17 2:39 dpdklab
2024-01-17 2:39 dpdklab
2024-01-17 2:42 dpdklab
2024-01-17 2:43 dpdklab
2024-01-17 2:43 dpdklab
2024-01-17 2:46 dpdklab
2024-01-17 2:46 dpdklab
2024-01-17 2:48 dpdklab
2024-01-17 2:48 dpdklab
2024-01-17 2:50 dpdklab
2024-01-17 2:50 dpdklab
2024-01-17 2:50 dpdklab
2024-01-17 2:51 dpdklab
2024-01-17 3:15 dpdklab
2024-01-17 3:36 dpdklab
2024-01-17 4:11 dpdklab
2024-01-17 4:50 dpdklab
2024-01-17 19:15 dpdklab
2024-01-17 22:48 dpdklab
2024-01-17 22:53 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=202401160611.40G6B8Bx1223550@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).