automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121067-121070 [PATCH v5 4/4] eventdev/timer: change eventdev reconfig logic
Date: Tue, 20 Dec 2022 17:04:41 +0800	[thread overview]
Message-ID: <202212200904.2BK94fca1213455@localhost.localdomain> (raw)
In-Reply-To: <20221220091137.3137300-4-s.v.naga.harish.k@intel.com>

Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/121070

_Compilation OK_

Submitter: Naga Harish K S V <s.v.naga.harish.k@intel.com>
Date: Tue, 20 Dec 2022 03:11:34 -0600
DPDK git baseline: Repo:dpdk-next-eventdev
  Branch: for-main
  CommitID: f262f16087ea6a77357a915cf4c0d10ddc7b6562

121067-121070 --> 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


       reply	other threads:[~2022-12-20  9:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221220091137.3137300-4-s.v.naga.harish.k@intel.com>
2022-12-20  9:04 ` qemudev [this message]
2022-12-20  9:08 ` qemudev
2022-12-20  9:12 ` |SUCCESS| pw121070 " checkpatch
2022-12-20 10:19 ` 0-day Robot
2022-12-20  9:41 |SUCCESS| pw121067-121070 [PATCH] [v5, " dpdklab
2022-12-20  9:41 dpdklab
2022-12-20  9:46 dpdklab
2022-12-20  9:48 dpdklab
2022-12-20  9:50 dpdklab
2022-12-20  9:57 dpdklab
2022-12-20 10:01 dpdklab
2022-12-20 11:04 dpdklab
2022-12-20 11:22 dpdklab
2022-12-20 11:22 dpdklab
2022-12-20 11:22 dpdklab
2022-12-20 11:22 dpdklab
2022-12-20 11:22 dpdklab
2022-12-20 12:03 dpdklab
2022-12-20 13:23 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=202212200904.2BK94fca1213455@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).