From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw142395 [PATCH] doc: update AMD Linux guide for power
Date: Sat, 13 Jul 2024 04:33:17 +0200 (CEST) [thread overview]
Message-ID: <20240713023318.1C4A4127EE2@dpdk.org> (raw)
In-Reply-To: <20240713023051.763-1-vipin.varghese@amd.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/142395
_coding style OK_
next prev parent reply other threads:[~2024-07-13 2:33 UTC|newest]
Thread overview: 115+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240713023051.763-1-vipin.varghese@amd.com>
2024-07-13 2:23 ` qemudev
2024-07-13 2:27 ` qemudev
2024-07-13 2:33 ` checkpatch [this message]
2024-07-13 3:07 ` dpdklab
2024-07-13 3:11 ` dpdklab
2024-07-13 3:12 ` |PENDING| " dpdklab
2024-07-13 3:14 ` dpdklab
2024-07-13 3:14 ` dpdklab
2024-07-13 3:17 ` dpdklab
2024-07-13 3:18 ` dpdklab
2024-07-13 3:19 ` dpdklab
2024-07-13 3:20 ` dpdklab
2024-07-13 3:20 ` dpdklab
2024-07-13 3:23 ` dpdklab
2024-07-13 3:24 ` |FAILURE| " 0-day Robot
2024-07-13 3:25 ` |PENDING| " dpdklab
2024-07-13 3:26 ` |SUCCESS| " dpdklab
2024-07-13 3:26 ` |PENDING| " dpdklab
2024-07-13 3:27 ` |SUCCESS| " dpdklab
2024-07-13 3:27 ` |PENDING| " dpdklab
2024-07-13 3:29 ` dpdklab
2024-07-13 3:29 ` |SUCCESS| " dpdklab
2024-07-13 3:30 ` |PENDING| " dpdklab
2024-07-13 3:30 ` dpdklab
2024-07-13 3:31 ` dpdklab
2024-07-13 3:31 ` dpdklab
2024-07-13 3:32 ` dpdklab
2024-07-13 3:33 ` dpdklab
2024-07-13 3:33 ` |SUCCESS| " dpdklab
2024-07-13 3:34 ` |PENDING| " dpdklab
2024-07-13 3:34 ` dpdklab
2024-07-13 3:35 ` dpdklab
2024-07-13 3:36 ` dpdklab
2024-07-13 3:36 ` dpdklab
2024-07-13 3:36 ` dpdklab
2024-07-13 3:36 ` dpdklab
2024-07-13 3:37 ` dpdklab
2024-07-13 3:37 ` dpdklab
2024-07-13 3:38 ` dpdklab
2024-07-13 3:39 ` dpdklab
2024-07-13 3:39 ` dpdklab
2024-07-13 3:39 ` dpdklab
2024-07-13 3:40 ` dpdklab
2024-07-13 3:40 ` dpdklab
2024-07-13 3:41 ` dpdklab
2024-07-13 3:41 ` dpdklab
2024-07-13 3:43 ` dpdklab
2024-07-13 3:43 ` dpdklab
2024-07-13 3:43 ` dpdklab
2024-07-13 3:44 ` dpdklab
2024-07-13 3:45 ` dpdklab
2024-07-13 3:45 ` dpdklab
2024-07-13 3:45 ` dpdklab
2024-07-13 3:49 ` dpdklab
2024-07-13 3:49 ` dpdklab
2024-07-13 3:50 ` dpdklab
2024-07-13 3:53 ` dpdklab
2024-07-13 3:53 ` |SUCCESS| " dpdklab
2024-07-13 3:54 ` |PENDING| " dpdklab
2024-07-13 3:54 ` dpdklab
2024-07-13 3:54 ` dpdklab
2024-07-13 3:55 ` dpdklab
2024-07-13 3:57 ` dpdklab
2024-07-13 4:01 ` dpdklab
2024-07-13 4:02 ` dpdklab
2024-07-13 4:04 ` dpdklab
2024-07-13 4:05 ` dpdklab
2024-07-13 4:05 ` dpdklab
2024-07-13 4:06 ` dpdklab
2024-07-13 4:08 ` dpdklab
2024-07-13 4:10 ` dpdklab
2024-07-13 4:10 ` dpdklab
2024-07-13 4:12 ` dpdklab
2024-07-13 4:12 ` dpdklab
2024-07-13 4:13 ` dpdklab
2024-07-13 4:13 ` dpdklab
2024-07-13 4:13 ` dpdklab
2024-07-13 4:14 ` dpdklab
2024-07-13 4:15 ` dpdklab
2024-07-13 4:16 ` dpdklab
2024-07-13 4:16 ` dpdklab
2024-07-13 4:17 ` dpdklab
2024-07-13 4:17 ` dpdklab
2024-07-13 4:17 ` dpdklab
2024-07-13 4:22 ` dpdklab
2024-07-13 4:22 ` dpdklab
2024-07-13 4:22 ` dpdklab
2024-07-13 4:23 ` dpdklab
2024-07-13 4:23 ` dpdklab
2024-07-13 4:24 ` dpdklab
2024-07-13 4:25 ` dpdklab
2024-07-13 4:26 ` |SUCCESS| " dpdklab
2024-07-13 4:28 ` |PENDING| " dpdklab
2024-07-13 4:31 ` |SUCCESS| " dpdklab
2024-07-13 4:31 ` |PENDING| " dpdklab
2024-07-13 4:32 ` dpdklab
2024-07-13 4:37 ` dpdklab
2024-07-13 4:39 ` dpdklab
2024-07-13 4:40 ` dpdklab
2024-07-13 4:40 ` |SUCCESS| " dpdklab
2024-07-13 4:43 ` |PENDING| " dpdklab
2024-07-13 4:45 ` dpdklab
2024-07-13 4:46 ` dpdklab
2024-07-13 4:47 ` dpdklab
2024-07-13 4:47 ` dpdklab
2024-07-13 4:52 ` dpdklab
2024-07-13 4:53 ` dpdklab
2024-07-13 4:56 ` dpdklab
2024-07-13 5:02 ` |SUCCESS| " dpdklab
2024-07-13 5:04 ` dpdklab
2024-07-15 14:07 ` dpdklab
2024-07-15 14:11 ` dpdklab
2024-07-15 14:31 ` dpdklab
2024-07-15 14:36 ` dpdklab
2024-07-15 14:42 ` 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=20240713023318.1C4A4127EE2@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).