automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw143378 [PATCH v1] net/ice: fix incorrect reading of PHY timestamp
Date: Fri, 23 Aug 2024 08:43:19 -0400	[thread overview]
Message-ID: <20240823124319.706090-1-robot@bytheb.org> (raw)
In-Reply-To: <20240823110133.456934-1-soumyadeep.hore@intel.com>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/143378/

_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/10525373124

  parent reply	other threads:[~2024-08-23 12:43 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240823110133.456934-1-soumyadeep.hore@intel.com>
2024-08-23 11:35 ` qemudev
2024-08-23 11:40 ` qemudev
2024-08-23 11:56 ` checkpatch
2024-08-23 12:43 ` 0-day Robot [this message]
2024-08-23 16:24 ` |SUCCESS| pw143378 [PATCH] [v1] net/ice: fix incorrect reading of PH dpdklab
2024-08-23 16:36 ` dpdklab
2024-08-23 16:55 ` dpdklab
2024-08-23 16:59 ` dpdklab
2024-08-23 17:02 ` dpdklab
2024-08-23 17:38 ` |FAILURE| " dpdklab
2024-08-23 19:15 ` |SUCCESS| " dpdklab
2024-08-23 19:17 ` dpdklab
2024-08-23 19:42 ` dpdklab
2024-08-23 19:51 ` dpdklab
2024-08-23 22:40 ` dpdklab
2024-08-23 22:46 ` dpdklab
2024-08-23 22:52 ` dpdklab
2024-08-23 23:00 ` dpdklab
2024-08-23 23:08 ` dpdklab
2024-08-23 23:17 ` dpdklab
2024-08-23 23:32 ` dpdklab
2024-08-23 23:34 ` dpdklab
2024-08-24  0:03 ` dpdklab
2024-08-24  0:06 ` dpdklab
2024-08-24  4:28 ` dpdklab
2024-08-24  4:29 ` |PENDING| " dpdklab
2024-08-24  4:37 ` dpdklab
2024-08-24  4:38 ` |FAILURE| " dpdklab
2024-08-24  4:42 ` dpdklab
2024-08-24  5:06 ` |WARNING| " dpdklab
2024-08-24  5:42 ` |SUCCESS| " dpdklab
2024-08-24  5:44 ` dpdklab
2024-08-24  6:18 ` |PENDING| " dpdklab
2024-08-24  7:11 ` |SUCCESS| " dpdklab
2024-08-24  7:22 ` dpdklab
2024-08-24  7:35 ` dpdklab
2024-08-24  7:57 ` dpdklab
2024-08-24  8:14 ` dpdklab
2024-08-24  8:25 ` dpdklab
2024-08-24  8:29 ` dpdklab
2024-08-24  8:32 ` dpdklab
2024-08-24  8:40 ` dpdklab
2024-08-24 12:17 ` dpdklab
2024-08-24 12:59 ` dpdklab
2024-08-26 14:33 ` dpdklab
2024-08-26 14:34 ` |WARNING| " dpdklab
2024-08-26 15:51 ` |SUCCESS| " dpdklab
2024-08-26 19:06 ` |WARNING| " dpdklab
2024-08-27  1:39 ` |SUCCESS| " dpdklab
2024-08-27  1:50 ` dpdklab
2024-08-27  1:54 ` dpdklab
2024-08-27  1:58 ` dpdklab
2024-08-27  2:02 ` dpdklab
2024-08-27  2:21 ` dpdklab
2024-08-27  2:59 ` dpdklab
2024-08-27 10:24 ` dpdklab
2024-08-27 14:23 ` 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=20240823124319.706090-1-robot@bytheb.org \
    --to=robot@bytheb.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).