automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw149264 [PATCH v2 5/5] eal/x86: defer power intrinsics variable allocation
Date: Tue, 17 Dec 2024 10:00:54 +0100 (CET)	[thread overview]
Message-ID: <20241217090054.5167F121F13@dpdk.org> (raw)
In-Reply-To: <20241217085954.3310414-6-david.marchand@redhat.com>

Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/149264

_coding style OK_



  parent reply	other threads:[~2024-12-17  9:01 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241217085954.3310414-6-david.marchand@redhat.com>
2024-12-17  8:29 ` |SUCCESS| pw149260-149264 " qemudev
2024-12-17  8:34 ` qemudev
2024-12-17  9:00 ` checkpatch [this message]
2024-12-17 10:03 ` |SUCCESS| pw149264 " 0-day Robot
2024-12-17 12:06 ` |SUCCESS| pw149260-149264 [PATCH] [v2,5/5] eal/x86: defer power intr dpdklab
2024-12-17 12:11 ` dpdklab
2024-12-17 12:22 ` dpdklab
2024-12-17 12:28 ` dpdklab
2024-12-17 12:32 ` dpdklab
2024-12-17 12:34 ` |FAILURE| " dpdklab
2024-12-17 12:34 ` |SUCCESS| " dpdklab
2024-12-17 12:49 ` dpdklab
2024-12-17 12:50 ` dpdklab
2024-12-17 12:50 ` dpdklab
2024-12-17 13:05 ` dpdklab
2024-12-17 13:07 ` dpdklab
2024-12-17 13:07 ` dpdklab
2024-12-17 13:08 ` dpdklab
2024-12-17 13:12 ` dpdklab
2024-12-17 13:16 ` dpdklab
2024-12-17 13:22 ` dpdklab
2024-12-17 13:24 ` dpdklab
2024-12-17 13:31 ` dpdklab
2024-12-17 13:41 ` |WARNING| " dpdklab
2024-12-17 13:45 ` |SUCCESS| " dpdklab
2024-12-17 13:46 ` |WARNING| " dpdklab
2024-12-17 13:46 ` |SUCCESS| " dpdklab
2024-12-17 13:54 ` dpdklab
2024-12-17 14:00 ` dpdklab
2024-12-17 14:42 ` dpdklab
2024-12-17 15:03 ` dpdklab
2024-12-17 15:08 ` dpdklab
2024-12-17 15:48 ` dpdklab
2024-12-17 16:35 ` |WARNING| " dpdklab
2024-12-17 16:57 ` 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=20241217090054.5167F121F13@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).