From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw138462 [PATCH v5 6/6] examples/vm_power_manager: fix lcore ID restriction
Date: Mon, 18 Mar 2024 18:34:25 +0100 (CET) [thread overview]
Message-ID: <20240318173425.D4B961223F7@dpdk.org> (raw)
In-Reply-To: <20240318173146.24303-7-sivaprasad.tummala@amd.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/138462
_coding style OK_
next prev parent reply other threads:[~2024-03-18 17:34 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240318173146.24303-7-sivaprasad.tummala@amd.com>
2024-03-18 17:11 ` |SUCCESS| pw138458-138462 " qemudev
2024-03-18 17:16 ` qemudev
2024-03-18 17:34 ` checkpatch [this message]
2024-03-18 18:23 ` |SUCCESS| pw138462 " 0-day Robot
2024-03-18 19:59 ` |SUCCESS| pw138458-138462 [PATCH] [v5,6/6] examples/vm_power_manager dpdklab
2024-03-18 20:00 ` dpdklab
2024-03-18 20:00 ` dpdklab
2024-03-18 20:01 ` dpdklab
2024-03-18 20:03 ` dpdklab
2024-03-18 20:03 ` dpdklab
2024-03-18 20:04 ` dpdklab
2024-03-18 20:08 ` dpdklab
2024-03-18 20:12 ` dpdklab
2024-03-18 20:16 ` dpdklab
2024-03-18 20:17 ` dpdklab
2024-03-18 20:17 ` dpdklab
2024-03-18 20:19 ` dpdklab
2024-03-18 20:19 ` dpdklab
2024-03-18 20:19 ` dpdklab
2024-03-18 20:20 ` dpdklab
2024-03-18 20:30 ` dpdklab
2024-03-18 20:32 ` dpdklab
2024-03-18 20:32 ` dpdklab
2024-03-18 20:33 ` dpdklab
2024-03-18 20:33 ` dpdklab
2024-03-18 20:34 ` dpdklab
2024-03-18 20:35 ` dpdklab
2024-03-18 20:36 ` dpdklab
2024-03-18 20:37 ` dpdklab
2024-03-18 20:37 ` dpdklab
2024-03-18 20:38 ` dpdklab
2024-03-18 20:38 ` dpdklab
2024-03-18 20:38 ` dpdklab
2024-03-18 20:39 ` dpdklab
2024-03-18 20:39 ` dpdklab
2024-03-18 20:39 ` dpdklab
2024-03-18 20:39 ` dpdklab
2024-03-18 20:40 ` dpdklab
2024-03-18 20:40 ` dpdklab
2024-03-18 20:41 ` dpdklab
2024-03-18 20:41 ` dpdklab
2024-03-18 20:41 ` dpdklab
2024-03-18 20:41 ` dpdklab
2024-03-18 20:41 ` dpdklab
2024-03-18 20:42 ` dpdklab
2024-03-18 20:42 ` dpdklab
2024-03-18 20:42 ` dpdklab
2024-03-18 20:42 ` dpdklab
2024-03-18 20:42 ` dpdklab
2024-03-18 20:43 ` dpdklab
2024-03-18 20:43 ` dpdklab
2024-03-18 20:43 ` dpdklab
2024-03-18 20:43 ` dpdklab
2024-03-18 20:43 ` dpdklab
2024-03-18 20:43 ` dpdklab
2024-03-18 20:44 ` dpdklab
2024-03-18 20:44 ` dpdklab
2024-03-18 20:44 ` dpdklab
2024-03-18 20:44 ` dpdklab
2024-03-18 20:44 ` dpdklab
2024-03-18 20:44 ` dpdklab
2024-03-18 20:44 ` dpdklab
2024-03-18 20:45 ` dpdklab
2024-03-18 20:45 ` dpdklab
2024-03-18 20:45 ` dpdklab
2024-03-18 20:45 ` dpdklab
2024-03-18 20:45 ` dpdklab
2024-03-18 20:45 ` dpdklab
2024-03-18 20:45 ` dpdklab
2024-03-18 20:46 ` dpdklab
2024-03-18 20:51 ` dpdklab
2024-03-18 20:56 ` dpdklab
2024-03-18 21:01 ` |FAILURE| " dpdklab
2024-03-18 21:02 ` |SUCCESS| " dpdklab
2024-03-18 21:14 ` |FAILURE| " dpdklab
2024-03-18 21:20 ` |SUCCESS| " dpdklab
2024-03-18 21:22 ` dpdklab
2024-03-18 23:31 ` dpdklab
2024-03-20 19:39 ` dpdklab
2024-03-20 20:13 ` 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=20240318173425.D4B961223F7@dpdk.org \
--to=checkpatch@dpdk.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).