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| pw158417 [PATCH v7 6/6] net/cnxk: report link mode
Date: Tue,  4 Nov 2025 05:45:32 -0500	[thread overview]
Message-ID: <20251104104532.3678956-1-robot@bytheb.org> (raw)
In-Reply-To: <20251104080901.1610706-6-skori@marvell.com>

From: robot@bytheb.org

Test-Label: github-robot-post
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/158417/

_github post: success_
HTML Link: https://github.com/ovsrobot/dpdk/pull/314

  parent reply	other threads:[~2025-11-04 10:45 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251104080901.1610706-6-skori@marvell.com>
2025-11-04  7:49 ` |SUCCESS| pw158413-158417 " qemudev
2025-11-04  7:57 ` |FAILURE| " qemudev
2025-11-04  8:09 ` |SUCCESS| pw158417 " checkpatch
2025-11-04  8:44 ` |PENDING| pw158413-158417 [PATCH] [v7,6/6] net/cnxk: report link mod dpdklab
2025-11-04  8:45 ` |SUCCESS| " dpdklab
2025-11-04  8:45 ` dpdklab
2025-11-04  8:53 ` dpdklab
2025-11-04  8:59 ` |PENDING| " dpdklab
2025-11-04  9:02 ` dpdklab
2025-11-04  9:13 ` |SUCCESS| " dpdklab
2025-11-04  9:18 ` dpdklab
2025-11-04  9:20 ` |PENDING| " dpdklab
2025-11-04  9:21 ` |SUCCESS| " dpdklab
2025-11-04  9:23 ` dpdklab
2025-11-04  9:24 ` dpdklab
2025-11-04  9:36 ` dpdklab
2025-11-04 10:22 ` dpdklab
2025-11-04 10:45 ` |SUCCESS| pw158417 [PATCH v7 6/6] net/cnxk: report link mode 0-day Robot
2025-11-04 10:45 ` 0-day Robot [this message]
2025-11-04 11:26 ` |SUCCESS| pw158413-158417 [PATCH] [v7,6/6] net/cnxk: report link mod dpdklab
2025-11-04 11:31 ` dpdklab
2025-11-04 11:35 ` dpdklab
2025-11-04 11:46 ` dpdklab
2025-11-04 11:57 ` dpdklab
2025-11-04 12:16 ` dpdklab
2025-11-04 12:36 ` dpdklab
2025-11-04 14:54 ` dpdklab
2025-11-04 18:33 ` 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=20251104104532.3678956-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).