From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw140672 [PATCH 2/2] eal: add Arm WFET in power management intrinsics
Date: Tue, 4 Jun 2024 02:26:51 -0400 [thread overview]
Message-ID: <20240604062651.3135130-1-robot@bytheb.org> (raw)
In-Reply-To: <20240604044401.3577707-2-wathsala.vithanage@arm.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/140672/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9361833049
next prev parent reply other threads:[~2024-06-04 6:26 UTC|newest]
Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240604044401.3577707-2-wathsala.vithanage@arm.com>
2024-06-04 4:37 ` |SUCCESS| pw140671-140672 " qemudev
2024-06-04 4:42 ` qemudev
2024-06-04 4:49 ` |SUCCESS| pw140672 " checkpatch
2024-06-04 5:45 ` |SUCCESS| pw140671-140672 [PATCH] [2/2] eal: add Arm WFET in power m dpdklab
2024-06-04 5:46 ` dpdklab
2024-06-04 5:46 ` dpdklab
2024-06-04 5:47 ` dpdklab
2024-06-04 5:48 ` dpdklab
2024-06-04 5:53 ` dpdklab
2024-06-04 6:03 ` dpdklab
2024-06-04 6:19 ` dpdklab
2024-06-04 6:21 ` dpdklab
2024-06-04 6:24 ` dpdklab
2024-06-04 6:26 ` dpdklab
2024-06-04 6:26 ` dpdklab
2024-06-04 6:26 ` 0-day Robot [this message]
2024-06-04 6:27 ` dpdklab
2024-06-04 6:29 ` dpdklab
2024-06-04 6:30 ` |FAILURE| " dpdklab
2024-06-04 6:30 ` |SUCCESS| " dpdklab
2024-06-04 6:32 ` dpdklab
2024-06-04 6:32 ` dpdklab
2024-06-04 6:34 ` dpdklab
2024-06-04 6:36 ` dpdklab
2024-06-04 6:38 ` dpdklab
2024-06-04 6:38 ` dpdklab
2024-06-04 6:46 ` dpdklab
2024-06-04 6:47 ` |FAILURE| " dpdklab
2024-06-04 6:47 ` |SUCCESS| " dpdklab
2024-06-04 6:47 ` |FAILURE| " dpdklab
2024-06-04 6:48 ` |SUCCESS| " dpdklab
2024-06-04 6:48 ` dpdklab
2024-06-04 6:48 ` dpdklab
2024-06-04 6:48 ` dpdklab
2024-06-04 6:48 ` dpdklab
2024-06-04 6:49 ` dpdklab
2024-06-04 6:50 ` |FAILURE| " dpdklab
2024-06-04 6:51 ` dpdklab
2024-06-04 6:58 ` |SUCCESS| " dpdklab
2024-06-04 7:03 ` dpdklab
2024-06-04 7:04 ` |FAILURE| " dpdklab
2024-06-04 7:23 ` dpdklab
2024-06-04 7:25 ` |SUCCESS| " dpdklab
2024-06-04 7:28 ` dpdklab
2024-06-04 7:30 ` dpdklab
2024-06-04 7:34 ` dpdklab
2024-06-04 7:40 ` dpdklab
2024-06-04 7:41 ` |FAILURE| " dpdklab
2024-06-04 7:42 ` dpdklab
2024-06-04 7:45 ` |SUCCESS| " dpdklab
2024-06-04 7:46 ` |FAILURE| " dpdklab
2024-06-04 7:57 ` |SUCCESS| " dpdklab
2024-06-04 7:58 ` |FAILURE| " dpdklab
2024-06-04 8:00 ` |SUCCESS| " dpdklab
2024-06-04 8:01 ` dpdklab
2024-06-04 8:05 ` |FAILURE| " dpdklab
2024-06-04 8:05 ` dpdklab
2024-06-04 8:08 ` |SUCCESS| " dpdklab
2024-06-04 8:13 ` dpdklab
2024-06-04 8:23 ` dpdklab
2024-06-04 8:23 ` dpdklab
2024-06-04 8:23 ` dpdklab
2024-06-04 8:23 ` dpdklab
2024-06-04 8:27 ` dpdklab
2024-06-04 8:28 ` dpdklab
2024-06-04 8:28 ` dpdklab
2024-06-04 8:29 ` dpdklab
2024-06-04 8:30 ` dpdklab
2024-06-04 8:30 ` |FAILURE| " dpdklab
2024-06-04 8:31 ` |SUCCESS| " dpdklab
2024-06-04 8:32 ` |FAILURE| " dpdklab
2024-06-04 8:32 ` |SUCCESS| " dpdklab
2024-06-04 8:33 ` |FAILURE| " dpdklab
2024-06-04 8:33 ` |SUCCESS| " dpdklab
2024-06-04 8:35 ` dpdklab
2024-06-04 8:36 ` dpdklab
2024-06-04 8:36 ` dpdklab
2024-06-04 8:38 ` dpdklab
2024-06-04 8:38 ` dpdklab
2024-06-04 8:41 ` dpdklab
2024-06-04 8:43 ` dpdklab
2024-06-04 8:43 ` dpdklab
2024-06-04 8:43 ` dpdklab
2024-06-04 8:55 ` dpdklab
2024-06-04 8:56 ` |FAILURE| " dpdklab
2024-06-04 8:57 ` |SUCCESS| " dpdklab
2024-06-04 9:04 ` dpdklab
2024-06-04 9:04 ` |FAILURE| " dpdklab
2024-06-04 9:08 ` |SUCCESS| " dpdklab
2024-06-04 9:25 ` |FAILURE| " dpdklab
2024-06-04 9:27 ` dpdklab
2024-06-04 10:05 ` dpdklab
2024-06-04 10:06 ` dpdklab
2024-06-04 10:14 ` dpdklab
2024-06-04 10:32 ` dpdklab
2024-06-04 10:36 ` dpdklab
2024-06-04 10:55 ` dpdklab
2024-06-04 11:22 ` dpdklab
2024-06-04 11:29 ` 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=20240604062651.3135130-1-robot@bytheb.org \
--to=robot@bytheb.org \
--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).