From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124879-124880 [PATCH 2/2] net/sfc: fix resetting mark in tunnel offload switch rules
Date: Thu, 9 Mar 2023 12:18:15 +0800 [thread overview]
Message-ID: <202303090418.3294IFrp1696099@localhost.localdomain> (raw)
In-Reply-To: <20230309042842.8709-2-ivan.malov@arknetworks.am>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124880
_Compilation OK_
Submitter: Ivan Malov <ivan.malov@arknetworks.am>
Date: Thu, 9 Mar 2023 08:28:41 +0400
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: cb318a8ab1b07ebefe9a85ae52552ba3ddbf8e7b
124879-124880 --> 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-03-09 4:32 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230309042842.8709-2-ivan.malov@arknetworks.am>
2023-03-09 4:18 ` qemudev [this message]
2023-03-09 4:22 ` qemudev
2023-03-09 4:28 ` |WARNING| pw124880 " checkpatch
2023-03-09 6:59 ` |SUCCESS| " 0-day Robot
2023-03-11 4:35 |SUCCESS| pw124879-124880 [PATCH] [2/2] " dpdklab
2023-03-11 4:39 dpdklab
2023-03-11 4:41 dpdklab
2023-03-11 4:43 dpdklab
2023-03-11 4:47 dpdklab
2023-03-11 4:50 dpdklab
2023-03-11 4:53 dpdklab
2023-03-11 4:54 dpdklab
2023-03-11 4:55 dpdklab
2023-03-11 5:14 dpdklab
2023-03-11 5:31 dpdklab
2023-03-11 5:36 dpdklab
2023-03-11 5:38 dpdklab
2023-03-11 5:44 dpdklab
2023-03-11 5:45 dpdklab
2023-03-11 5:49 dpdklab
2023-03-11 5:50 dpdklab
2023-03-11 5:50 dpdklab
2023-03-11 5:55 dpdklab
2023-03-11 5:55 dpdklab
2023-03-11 5:55 dpdklab
2023-03-11 5:56 dpdklab
2023-03-11 5:58 dpdklab
2023-03-11 6:00 dpdklab
2023-03-11 6:05 dpdklab
2023-03-11 6:17 dpdklab
2023-03-11 6:29 dpdklab
2023-03-11 7:20 dpdklab
2023-03-12 4:20 dpdklab
2023-03-12 4:41 dpdklab
2023-03-12 5:14 dpdklab
2023-03-12 6:02 dpdklab
2023-03-12 14:23 dpdklab
2023-03-12 14:24 dpdklab
2023-03-12 14:26 dpdklab
2023-03-12 14:34 dpdklab
2023-03-12 14:40 dpdklab
2023-03-12 14:43 dpdklab
2023-03-12 14:44 dpdklab
2023-03-12 14:46 dpdklab
2023-03-12 14:49 dpdklab
2023-03-12 14:53 dpdklab
2023-03-12 14:55 dpdklab
2023-03-12 14:55 dpdklab
2023-03-12 15:28 dpdklab
2023-03-12 15:34 dpdklab
2023-03-12 15:34 dpdklab
2023-03-12 15:34 dpdklab
2023-03-12 15:39 dpdklab
2023-03-12 15:40 dpdklab
2023-03-12 15:42 dpdklab
2023-03-12 15:47 dpdklab
2023-03-12 15:49 dpdklab
2023-03-12 15:51 dpdklab
2023-03-12 16:02 dpdklab
2023-03-12 16:05 dpdklab
2023-03-12 16:07 dpdklab
2023-03-12 16:15 dpdklab
2023-03-12 16:43 dpdklab
2023-03-12 16:44 dpdklab
2023-03-13 4:59 dpdklab
2023-03-13 6:34 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=202303090418.3294IFrp1696099@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).