From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122940 [PATCH V8] ethdev: fix one address occupies two entries in MAC addrs
Date: Thu, 2 Feb 2023 20:49:43 +0800 [thread overview]
Message-ID: <202302021249.312CnhaF678255@localhost.localdomain> (raw)
In-Reply-To: <20230202123625.14975-1-lihuisong@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/122940
_Compilation OK_
Submitter: Huisong Li <lihuisong@huawei.com>
Date: Thu, 2 Feb 2023 20:36:25 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 8865a5a6e68b54c298987f07d2604c62eda8bffd
122940 --> 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-02-03 4:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230202123625.14975-1-lihuisong@huawei.com>
2023-02-02 12:38 ` checkpatch
2023-02-02 12:49 ` qemudev [this message]
2023-02-02 12:55 ` qemudev
2023-02-02 14:19 ` 0-day Robot
2023-02-04 17:36 |SUCCESS| pw122940 [PATCH] [V8] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-02-04 16:41 dpdklab
2023-02-04 6:59 dpdklab
2023-02-03 12:21 dpdklab
2023-02-03 12:21 dpdklab
2023-02-03 12:21 dpdklab
2023-02-03 12:21 dpdklab
2023-02-03 12:20 dpdklab
2023-02-03 12:20 dpdklab
2023-02-03 12:20 dpdklab
2023-02-03 12:20 dpdklab
2023-02-03 12:20 dpdklab
2023-02-03 12:20 dpdklab
2023-02-03 10:20 dpdklab
2023-02-02 16:42 dpdklab
2023-02-02 14:55 dpdklab
2023-02-02 14:38 dpdklab
2023-02-02 14:34 dpdklab
2023-02-02 14:25 dpdklab
2023-02-02 14:21 dpdklab
2023-02-02 14:18 dpdklab
2023-02-02 13:59 dpdklab
2023-02-02 13:43 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=202302021249.312CnhaF678255@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).