automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw125231 [PATCH v6] eal/unix: fix thread creation
Date: Fri, 17 Mar 2023 19:54:10 +0100 (CET)	[thread overview]
Message-ID: <20230317185410.33F4B1209C6@dpdk.org> (raw)
In-Reply-To: <20230317185229.449011-1-david.marchand@redhat.com>

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

_coding style OK_



  parent reply	other threads:[~2023-03-17 18:54 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230317185229.449011-1-david.marchand@redhat.com>
2023-03-17 18:41 ` qemudev
2023-03-17 18:45 ` qemudev
2023-03-17 18:54 ` checkpatch [this message]
2023-03-17 21:19 ` 0-day Robot
2023-03-17 19:44 |SUCCESS| pw125231 [PATCH] [v6] " dpdklab
2023-03-17 19:50 dpdklab
2023-03-17 19:51 dpdklab
2023-03-17 19:57 dpdklab
2023-03-17 19:57 dpdklab
2023-03-17 19:57 dpdklab
2023-03-17 19:59 dpdklab
2023-03-17 19:59 dpdklab
2023-03-17 20:01 dpdklab
2023-03-17 20:03 dpdklab
2023-03-17 20:03 dpdklab
2023-03-17 20:06 dpdklab
2023-03-17 20:06 dpdklab
2023-03-17 20:09 dpdklab
2023-03-17 20:12 dpdklab
2023-03-17 20:12 dpdklab
2023-03-17 20:12 dpdklab
2023-03-17 20:12 dpdklab
2023-03-17 20:16 dpdklab
2023-03-17 20:21 dpdklab
2023-03-17 20:25 dpdklab
2023-03-17 20:25 dpdklab
2023-03-17 20:28 dpdklab
2023-03-17 20:29 dpdklab
2023-03-17 20:29 dpdklab
2023-03-17 20:30 dpdklab
2023-03-17 20:42 dpdklab
2023-03-17 20:45 dpdklab
2023-03-17 20:49 dpdklab
2023-03-17 20:49 dpdklab
2023-03-19 14:56 dpdklab
2023-03-19 15:03 dpdklab
2023-03-20  3:21 dpdklab
2023-03-20  4:40 dpdklab
2023-03-21 21:27 dpdklab
2023-03-21 22:38 dpdklab
2023-03-21 22:38 dpdklab
2023-03-22  3:46 dpdklab
2023-03-22  3:54 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=20230317185410.33F4B1209C6@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).