From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121580-121585 [PATCH v1 6/6] baseband/acc: acc100 fix queue mapping to 64 bits
Date: Thu, 5 Jan 2023 00:12:09 +0800 [thread overview]
Message-ID: <202301041612.304GC91Y3393874@localhost.localdomain> (raw)
In-Reply-To: <20230105001109.120564-7-hernan.vargas@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/121585
_Compilation OK_
Submitter: Hernan Vargas <hernan.vargas@intel.com>
Date: Wed, 4 Jan 2023 16:11:04 -0800
DPDK git baseline: Repo:dpdk-next-baseband
Branch: for-main
CommitID: dc0a5a0d2a227c8616abdb5c98220b1bf1594d23
121580-121585 --> 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-04 16:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230105001109.120564-7-hernan.vargas@intel.com>
2023-01-04 16:12 ` qemudev [this message]
2023-01-04 16:16 ` qemudev
2023-01-04 16:17 ` |SUCCESS| pw121585 " checkpatch
2023-01-04 16:59 ` 0-day Robot
2023-01-05 13:26 |SUCCESS| pw121580-121585 [PATCH] [v1, " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-01-05 11:20 dpdklab
2023-01-05 9:47 dpdklab
2023-01-05 2:02 dpdklab
2023-01-05 2:01 dpdklab
2023-01-05 2:01 dpdklab
2023-01-05 1:53 dpdklab
2023-01-05 1:53 dpdklab
2023-01-05 1:53 dpdklab
2023-01-05 1:53 dpdklab
2023-01-05 1:53 dpdklab
2023-01-05 1:52 dpdklab
2023-01-05 1:38 dpdklab
2023-01-04 18:41 dpdklab
2023-01-04 17:02 dpdklab
2023-01-04 16:57 dpdklab
2023-01-04 16:55 dpdklab
2023-01-04 16:50 dpdklab
2023-01-04 16:48 dpdklab
2023-01-04 16:43 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=202301041612.304GC91Y3393874@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).