From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw128982 [PATCH] net/idpf: refine dev_link_update function
Date: Mon, 26 Jun 2023 10:45:12 +0800 [thread overview]
Message-ID: <202306260245.35Q2jCIN362567@localhost.localdomain> (raw)
In-Reply-To: <20230626111454.489844-1-mingxia.liu@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/128982
_Compilation OK_
Submitter: Mingxia Liu <mingxia.liu@intel.com>
Date: Mon, 26 Jun 2023 11:14:54 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: ca86455d29fa7319616d9f37662c76ca47fdf338
128982 --> 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-06-26 2:59 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230626111454.489844-1-mingxia.liu@intel.com>
2023-06-26 2:45 ` qemudev [this message]
2023-06-26 2:49 ` qemudev
2023-06-26 2:58 ` checkpatch
2023-06-26 3:59 ` 0-day Robot
2023-06-26 3:24 dpdklab
2023-06-26 3:26 dpdklab
2023-06-26 3:28 dpdklab
2023-06-26 3:29 dpdklab
2023-06-26 3:29 dpdklab
2023-06-26 3:36 dpdklab
2023-06-26 3:38 dpdklab
2023-06-26 3:45 dpdklab
2023-06-26 3:46 dpdklab
2023-06-26 3:47 dpdklab
2023-06-26 3:47 dpdklab
2023-06-26 3:49 dpdklab
2023-06-26 3:50 dpdklab
2023-06-26 3:51 dpdklab
2023-06-26 3:52 dpdklab
2023-06-26 3:54 dpdklab
2023-06-26 3:56 dpdklab
2023-06-26 3:57 dpdklab
2023-06-26 3:58 dpdklab
2023-06-26 4:00 dpdklab
2023-06-26 4:01 dpdklab
2023-06-26 4:06 dpdklab
2023-06-26 4:06 dpdklab
2023-06-26 4:06 dpdklab
2023-06-26 4:10 dpdklab
2023-06-26 4:26 dpdklab
2023-06-26 4:28 dpdklab
2023-06-26 6:07 dpdklab
2023-06-26 16:28 dpdklab
2023-06-26 16:47 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=202306260245.35Q2jCIN362567@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).