From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121553-121556 [PATCH v6 4/4] eventdev/timer: change eventdev reconfig logic
Date: Wed, 4 Jan 2023 14:34:45 +0800 [thread overview]
Message-ID: <202301040634.3046YjgT2835487@localhost.localdomain> (raw)
In-Reply-To: <20230104064145.2600261-4-s.v.naga.harish.k@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/121556
_Compilation OK_
Submitter: Naga Harish K S V <s.v.naga.harish.k@intel.com>
Date: Wed, 4 Jan 2023 00:41:42 -0600
DPDK git baseline: Repo:dpdk-next-eventdev
Branch: for-main
CommitID: 373f4c7de8ff350548cacc3d56e788461677f2c7
121553-121556 --> 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 6:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230104064145.2600261-4-s.v.naga.harish.k@intel.com>
2023-01-04 6:34 ` qemudev [this message]
2023-01-04 6:38 ` qemudev
2023-01-04 6:43 ` |SUCCESS| pw121556 " checkpatch
2023-01-04 7:39 ` 0-day Robot
2023-01-04 7:14 |SUCCESS| pw121553-121556 [PATCH] [v6, " dpdklab
2023-01-04 7:16 dpdklab
2023-01-04 7:29 dpdklab
2023-01-04 7:45 dpdklab
2023-01-04 7:46 dpdklab
2023-01-04 8:06 dpdklab
2023-01-04 11:05 dpdklab
2023-01-04 13:16 dpdklab
2023-01-04 13:17 dpdklab
2023-01-04 13:18 dpdklab
2023-01-04 13:18 dpdklab
2023-01-04 13:18 dpdklab
2023-01-04 13:19 dpdklab
2023-01-04 13:19 dpdklab
2023-01-04 13:29 dpdklab
2023-01-04 13:29 dpdklab
2023-01-04 13:29 dpdklab
2023-01-04 21:04 dpdklab
2023-01-04 22:23 dpdklab
2023-01-04 23:55 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=202301040634.3046YjgT2835487@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).