automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw142803 [PATCH v1] net/ice: fix ice Rx timestamp for E822 NICs
Date: Thu,  1 Aug 2024 07:31:35 +0200 (CEST)	[thread overview]
Message-ID: <20240801053135.C8416123EF2@dpdk.org> (raw)
In-Reply-To: <20240801044015.3204579-1-soumyadeep.hore@intel.com>

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

_coding style OK_



  parent reply	other threads:[~2024-08-01  5:31 UTC|newest]

Thread overview: 109+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240801044015.3204579-1-soumyadeep.hore@intel.com>
2024-08-01  5:05 ` qemudev
2024-08-01  5:09 ` qemudev
2024-08-01  5:31 ` checkpatch [this message]
2024-08-01  6:22 ` 0-day Robot
2024-08-01  7:55 ` |SUCCESS| pw142803 [PATCH] [v1] net/ice: fix ice Rx timestamp for E8 dpdklab
2024-08-01  7:57 ` |PENDING| " dpdklab
2024-08-01  8:00 ` dpdklab
2024-08-01  8:10 ` |SUCCESS| " dpdklab
2024-08-01  8:14 ` dpdklab
2024-08-01  8:32 ` dpdklab
2024-08-01  9:59 ` |PENDING| " dpdklab
2024-08-01 10:07 ` |SUCCESS| " dpdklab
2024-08-01 10:41 ` dpdklab
2024-08-01 11:17 ` |PENDING| " dpdklab
2024-08-01 11:20 ` dpdklab
2024-08-01 11:21 ` dpdklab
2024-08-01 11:22 ` dpdklab
2024-08-01 11:25 ` dpdklab
2024-08-01 11:27 ` dpdklab
2024-08-01 11:29 ` |SUCCESS| " dpdklab
2024-08-01 11:32 ` |PENDING| " dpdklab
2024-08-01 11:32 ` dpdklab
2024-08-01 11:33 ` dpdklab
2024-08-01 11:36 ` dpdklab
2024-08-01 11:39 ` dpdklab
2024-08-01 11:40 ` dpdklab
2024-08-01 11:46 ` dpdklab
2024-08-01 11:53 ` dpdklab
2024-08-01 11:57 ` dpdklab
2024-08-01 12:00 ` dpdklab
2024-08-01 12:00 ` dpdklab
2024-08-01 12:02 ` dpdklab
2024-08-01 12:02 ` dpdklab
2024-08-01 12:03 ` dpdklab
2024-08-01 12:03 ` dpdklab
2024-08-01 12:03 ` dpdklab
2024-08-01 12:05 ` dpdklab
2024-08-01 12:06 ` dpdklab
2024-08-01 12:06 ` dpdklab
2024-08-01 12:07 ` dpdklab
2024-08-01 12:07 ` dpdklab
2024-08-01 12:09 ` dpdklab
2024-08-01 12:09 ` dpdklab
2024-08-01 12:10 ` dpdklab
2024-08-01 12:11 ` dpdklab
2024-08-01 12:12 ` dpdklab
2024-08-01 12:14 ` dpdklab
2024-08-01 12:15 ` dpdklab
2024-08-01 12:15 ` dpdklab
2024-08-01 12:15 ` dpdklab
2024-08-01 12:16 ` dpdklab
2024-08-01 12:16 ` dpdklab
2024-08-01 12:17 ` dpdklab
2024-08-01 12:17 ` dpdklab
2024-08-01 12:17 ` dpdklab
2024-08-01 12:18 ` dpdklab
2024-08-01 12:20 ` dpdklab
2024-08-01 12:40 ` |SUCCESS| " dpdklab
2024-08-01 12:46 ` dpdklab
2024-08-01 12:49 ` |PENDING| " dpdklab
2024-08-01 12:50 ` dpdklab
2024-08-01 12:54 ` dpdklab
2024-08-01 13:04 ` |SUCCESS| " dpdklab
2024-08-01 13:25 ` |PENDING| " dpdklab
2024-08-01 13:33 ` dpdklab
2024-08-01 13:38 ` dpdklab
2024-08-01 13:39 ` dpdklab
2024-08-01 13:40 ` dpdklab
2024-08-01 13:43 ` dpdklab
2024-08-01 13:47 ` dpdklab
2024-08-01 13:52 ` dpdklab
2024-08-01 13:52 ` dpdklab
2024-08-01 13:55 ` dpdklab
2024-08-01 13:56 ` dpdklab
2024-08-01 13:58 ` dpdklab
2024-08-01 14:02 ` dpdklab
2024-08-01 14:02 ` dpdklab
2024-08-01 14:03 ` dpdklab
2024-08-01 14:03 ` dpdklab
2024-08-01 14:04 ` dpdklab
2024-08-01 14:05 ` dpdklab
2024-08-01 14:05 ` dpdklab
2024-08-01 14:06 ` dpdklab
2024-08-01 14:06 ` dpdklab
2024-08-01 14:08 ` dpdklab
2024-08-01 14:10 ` dpdklab
2024-08-01 14:11 ` dpdklab
2024-08-01 14:12 ` dpdklab
2024-08-01 14:16 ` dpdklab
2024-08-01 14:16 ` dpdklab
2024-08-01 14:17 ` dpdklab
2024-08-01 14:17 ` dpdklab
2024-08-01 14:21 ` dpdklab
2024-08-01 14:23 ` |SUCCESS| " dpdklab
2024-08-01 14:24 ` |PENDING| " dpdklab
2024-08-01 14:24 ` dpdklab
2024-08-01 14:28 ` dpdklab
2024-08-01 14:28 ` dpdklab
2024-08-01 14:29 ` |SUCCESS| " dpdklab
2024-08-01 14:29 ` |PENDING| " dpdklab
2024-08-01 14:29 ` dpdklab
2024-08-01 14:35 ` dpdklab
2024-08-01 14:37 ` dpdklab
2024-08-01 14:40 ` |SUCCESS| " dpdklab
2024-08-01 15:25 ` dpdklab
2024-08-02 19:16 ` dpdklab
2024-08-05 22:26 ` dpdklab
2024-08-05 22:34 ` dpdklab
2024-08-05 22:48 ` 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=20240801053135.C8416123EF2@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).