From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123897 [PATCH] net/sfc: fix MAC address entry leak in transfer flow parsing
Date: Tue, 14 Feb 2023 20:57:07 +0800 [thread overview]
Message-ID: <202302141257.31ECv7nA4066878@localhost.localdomain> (raw)
In-Reply-To: <20230214130659.6971-1-ivan.malov@arknetworks.am>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123897
_Compilation OK_
Submitter: Ivan Malov <ivan.malov@arknetworks.am>
Date: Tue, 14 Feb 2023 17:06:59 +0400
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 92bdd498d04271b1d7e8d32a8ca7ffb1bedd31f3
123897 --> 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-02-14 13:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230214130659.6971-1-ivan.malov@arknetworks.am>
2023-02-14 12:57 ` qemudev [this message]
2023-02-14 13:01 ` qemudev
2023-02-14 13:07 ` |WARNING| " checkpatch
2023-02-14 15:19 ` |SUCCESS| " 0-day Robot
2023-02-14 13:27 dpdklab
2023-02-14 13:30 dpdklab
2023-02-14 13:31 dpdklab
2023-02-14 13:37 dpdklab
2023-02-14 13:40 dpdklab
2023-02-14 13:43 dpdklab
2023-02-14 13:44 dpdklab
2023-02-14 13:47 dpdklab
2023-02-14 13:51 dpdklab
2023-02-14 15:02 dpdklab
2023-02-14 15:04 dpdklab
2023-02-14 15:08 dpdklab
2023-02-14 15:27 dpdklab
2023-02-14 15:29 dpdklab
2023-02-14 15:36 dpdklab
2023-02-14 15:39 dpdklab
2023-02-14 15:40 dpdklab
2023-02-14 15:52 dpdklab
2023-02-16 7:39 dpdklab
2023-02-17 2:06 dpdklab
2023-02-18 10:01 dpdklab
2023-02-22 18:50 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=202302141257.31ECv7nA4066878@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).