From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw143034-143036 [PATCH v3 3/3] net/enic: allow multicast in MAC address add callback
Date: Fri, 9 Aug 2024 14:42:27 +0800 [thread overview]
Message-ID: <202408090642.4796gRHX3744006@localhost.localdomain> (raw)
In-Reply-To: <20240809070754.26128-4-hyonkim@cisco.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/143036
_Compilation OK_
Submitter: Hyong Youb Kim <hyonkim@cisco.com>
Date: Fri, 9 Aug 2024 00:07:52 -0700
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: e0f7ebe88ab4588dd352e9ec14270ce4e3b1470b
143034-143036 --> 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-08-09 7:11 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240809070754.26128-4-hyonkim@cisco.com>
2024-08-09 6:42 ` qemudev [this message]
2024-08-09 6:46 ` qemudev
2024-08-09 7:09 ` |SUCCESS| pw143036 " checkpatch
2024-08-09 8:02 ` 0-day Robot
2024-08-09 9:09 ` |SUCCESS| pw143034-143036 [PATCH] [v3,3/3] net/enic: allow multicast dpdklab
2024-08-09 9:13 ` dpdklab
2024-08-09 9:14 ` dpdklab
2024-08-09 9:16 ` |PENDING| " dpdklab
2024-08-09 9:18 ` |SUCCESS| " dpdklab
2024-08-09 9:18 ` dpdklab
2024-08-09 9:24 ` dpdklab
2024-08-09 9:31 ` dpdklab
2024-08-09 9:32 ` dpdklab
2024-08-09 9:34 ` dpdklab
2024-08-09 10:00 ` dpdklab
2024-08-09 10:44 ` |WARNING| " dpdklab
2024-08-09 10:53 ` |SUCCESS| " dpdklab
2024-08-09 11:01 ` |WARNING| " dpdklab
2024-08-09 11:05 ` dpdklab
2024-08-09 11:06 ` dpdklab
2024-08-09 11:10 ` dpdklab
2024-08-09 11:11 ` dpdklab
2024-08-09 11:11 ` dpdklab
2024-08-09 11:12 ` dpdklab
2024-08-09 11:14 ` dpdklab
2024-08-09 11:17 ` dpdklab
2024-08-09 11:17 ` dpdklab
2024-08-09 11:19 ` dpdklab
2024-08-09 11:26 ` dpdklab
2024-08-09 11:31 ` |SUCCESS| " dpdklab
2024-08-09 11:37 ` dpdklab
2024-08-09 12:06 ` dpdklab
2024-08-09 12:25 ` |WARNING| " dpdklab
2024-08-09 12:36 ` |SUCCESS| " dpdklab
2024-08-09 12:56 ` dpdklab
2024-08-09 16:09 ` |PENDING| " dpdklab
2024-08-09 16:10 ` dpdklab
2024-08-09 16:14 ` dpdklab
2024-08-09 16:19 ` dpdklab
2024-08-09 16:19 ` dpdklab
2024-08-09 16:23 ` dpdklab
2024-08-09 16:49 ` dpdklab
2024-08-09 18:02 ` dpdklab
2024-08-09 18:06 ` dpdklab
2024-08-09 18:07 ` dpdklab
2024-08-09 18:09 ` dpdklab
2024-08-09 18:10 ` dpdklab
2024-08-09 18:14 ` dpdklab
2024-08-09 18:14 ` dpdklab
2024-08-09 18:15 ` dpdklab
2024-08-09 18:16 ` dpdklab
2024-08-09 18:16 ` dpdklab
2024-08-09 18:19 ` dpdklab
2024-08-09 18:19 ` dpdklab
2024-08-09 18:19 ` dpdklab
2024-08-09 18:21 ` dpdklab
2024-08-09 18:21 ` dpdklab
2024-08-09 18:23 ` dpdklab
2024-08-09 18:23 ` dpdklab
2024-08-09 18:24 ` dpdklab
2024-08-09 18:24 ` dpdklab
2024-08-09 18:25 ` dpdklab
2024-08-09 18:25 ` dpdklab
2024-08-09 18:26 ` dpdklab
2024-08-09 18:27 ` dpdklab
2024-08-09 18:29 ` dpdklab
2024-08-09 18:29 ` dpdklab
2024-08-09 18:30 ` dpdklab
2024-08-09 18:30 ` dpdklab
2024-08-09 18:32 ` dpdklab
2024-08-09 18:32 ` dpdklab
2024-08-09 18:33 ` dpdklab
2024-08-09 18:33 ` dpdklab
2024-08-09 18:33 ` dpdklab
2024-08-09 18:33 ` dpdklab
2024-08-09 18:37 ` dpdklab
2024-08-09 18:38 ` dpdklab
2024-08-09 18:41 ` dpdklab
2024-08-09 18:42 ` dpdklab
2024-08-09 18:47 ` dpdklab
2024-08-09 18:50 ` dpdklab
2024-08-09 19:02 ` dpdklab
2024-08-09 19:03 ` |SUCCESS| " dpdklab
2024-08-09 19:16 ` |PENDING| " dpdklab
2024-08-09 19:25 ` dpdklab
2024-08-09 19:42 ` dpdklab
2024-08-09 19:45 ` |SUCCESS| " dpdklab
2024-08-09 19:47 ` |PENDING| " dpdklab
2024-08-09 19:53 ` dpdklab
2024-08-09 20:01 ` dpdklab
2024-08-09 21:20 ` dpdklab
2024-08-10 2:03 ` |SUCCESS| " 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=202408090642.4796gRHX3744006@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).