From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124755 [PATCH] net/mana: use trace points for data path logs
Date: Mon, 6 Mar 2023 15:14:18 +0800 [thread overview]
Message-ID: <202303060714.3267EIDx3957420@localhost.localdomain> (raw)
In-Reply-To: <1677809657-26847-1-git-send-email-longli@linuxonhyperv.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124755
_Compilation OK_
Submitter: Long Li <longli@linuxonhyperv.com>
Date: Thu, 2 Mar 2023 18:14:17 -0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: abf68fdaf5ec0b2e7ef2297ad57c4d4991ae3b45
124755 --> 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 prev parent reply other threads:[~2023-03-06 7:28 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1677809657-26847-1-git-send-email-longli@linuxonhyperv.com>
2023-03-03 2:14 ` |WARNING| " checkpatch
2023-03-03 3:59 ` |SUCCESS| " 0-day Robot
2023-03-06 7:14 ` qemudev [this message]
2023-03-06 7:14 ` qemudev
2023-03-04 18:17 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-03-04 18:05 dpdklab
2023-03-04 18:03 dpdklab
2023-03-04 17:59 dpdklab
2023-03-04 17:58 dpdklab
2023-03-04 17:56 dpdklab
2023-03-04 17:55 dpdklab
2023-03-04 17:54 dpdklab
2023-03-04 17:53 dpdklab
2023-03-04 17:50 dpdklab
2023-03-04 17:50 dpdklab
2023-03-04 17:40 dpdklab
2023-03-04 17:38 dpdklab
2023-03-04 17:32 dpdklab
2023-03-04 17:32 dpdklab
2023-03-04 17:17 dpdklab
2023-03-04 17:09 dpdklab
2023-03-04 17:07 dpdklab
2023-03-04 17:04 dpdklab
2023-03-04 17:01 dpdklab
2023-03-04 16:56 dpdklab
2023-03-04 16:54 dpdklab
2023-03-04 16:53 dpdklab
2023-03-04 16:52 dpdklab
2023-03-04 16:51 dpdklab
2023-03-04 16:45 dpdklab
2023-03-03 17:06 dpdklab
2023-03-03 16:05 dpdklab
2023-03-03 9:10 dpdklab
2023-03-03 6:55 dpdklab
2023-03-03 6:01 dpdklab
2023-03-03 4:52 dpdklab
2023-03-03 4:52 dpdklab
2023-03-03 4:30 dpdklab
2023-03-03 4:15 dpdklab
2023-03-03 4:11 dpdklab
2023-03-03 4:03 dpdklab
2023-03-03 4:02 dpdklab
2023-03-03 4:00 dpdklab
2023-03-03 3:58 dpdklab
2023-03-03 3:56 dpdklab
2023-03-03 3:55 dpdklab
2023-03-03 3:55 dpdklab
2023-03-03 3:53 dpdklab
2023-03-03 3:51 dpdklab
2023-03-03 3:44 dpdklab
2023-03-03 3:39 dpdklab
2023-03-03 3:34 dpdklab
2023-03-03 3:28 dpdklab
2023-03-03 3:26 dpdklab
2023-03-03 3:25 dpdklab
2023-03-03 3:24 dpdklab
2023-03-03 3:22 dpdklab
2023-03-03 3:20 dpdklab
2023-03-03 3:20 dpdklab
2023-03-03 3:17 dpdklab
2023-03-03 3:16 dpdklab
2023-03-03 3:14 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=202303060714.3267EIDx3957420@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).