From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw128724-128725 [PATCH 2/2] net/iavf: fix variable type in pattern parsing for raw flow
Date: Thu, 15 Jun 2023 13:06:22 +0800 [thread overview]
Message-ID: <202306150506.35F56MDe3587670@localhost.localdomain> (raw)
In-Reply-To: <20230615051717.2906443-3-junfeng.guo@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/128725
_Compilation OK_
Submitter: Junfeng Guo <junfeng.guo@intel.com>
Date: Thu, 15 Jun 2023 13:17:16 +0800
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 9712fdb14441c07f1e966a08d2947a2b12ce3f28
128724-128725 --> 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-06-15 5:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230615051717.2906443-3-junfeng.guo@intel.com>
2023-06-15 5:06 ` qemudev [this message]
2023-06-15 5:10 ` qemudev
2023-06-15 5:17 ` |SUCCESS| pw128725 " checkpatch
2023-06-15 6:39 ` 0-day Robot
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=202306150506.35F56MDe3587670@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).