From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121805-121808 [PATCH v2 4/4] common/cnxk: fix dual VLAN parsing issue
Date: Wed, 11 Jan 2023 13:30:09 +0800 [thread overview]
Message-ID: <202301110530.30B5U9tG2002374@localhost.localdomain> (raw)
In-Reply-To: <20230111053814.979400-4-psatheesh@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/121808
_Compilation OK_
Submitter: Satheesh Paul Antonysamy <psatheesh@marvell.com>
Date: Wed, 11 Jan 2023 11:08:11 +0530
DPDK git baseline: Repo:dpdk-next-net-mrvl
Branch: for-next-net
CommitID: 534015c76e87842f3673f39393e9b0ac4b20eba8
121805-121808 --> 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-01-11 5:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230111053814.979400-4-psatheesh@marvell.com>
2023-01-11 5:30 ` qemudev [this message]
2023-01-11 5:34 ` qemudev
2023-01-11 5:38 ` |SUCCESS| pw121808 " checkpatch
2023-01-11 6:59 ` |SUCCESS| pw121808 [dpdk-dev] " 0-day Robot
2023-01-11 6:15 |SUCCESS| pw121805-121808 [PATCH] [v2, " dpdklab
2023-01-11 6:18 dpdklab
2023-01-11 6:33 dpdklab
2023-01-11 6:40 dpdklab
2023-01-11 6:41 dpdklab
2023-01-11 6:48 dpdklab
2023-01-11 8:22 dpdklab
2023-01-11 8:46 dpdklab
2023-01-11 9:21 dpdklab
2023-01-11 9:24 dpdklab
2023-01-11 9:24 dpdklab
2023-01-11 9:24 dpdklab
2023-01-11 9:25 dpdklab
2023-01-11 10:06 dpdklab
2023-01-11 10:13 dpdklab
2023-01-11 10:25 dpdklab
2023-01-11 10:25 dpdklab
2023-01-11 15:36 dpdklab
2023-01-11 15:46 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=202301110530.30B5U9tG2002374@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).