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| pw157390 [PATCH v11 21/21] eal: allow lcore remapping with autodetected core affinity
Date: Thu,  9 Oct 2025 10:59:43 -0400	[thread overview]
Message-ID: <20251009145943.2968049-1-robot@bytheb.org> (raw)
In-Reply-To: <20251009130056.2630343-22-bruce.richardson@intel.com>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2025-10-09 14:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251009130056.2630343-22-bruce.richardson@intel.com>
2025-10-09 12:30 ` |SUCCESS| pw157370-157390 " qemudev
2025-10-09 12:35 ` qemudev
2025-10-09 13:04 ` |SUCCESS| pw157390 " checkpatch
2025-10-09 13:29 ` |PENDING| pw157370-157390 [PATCH] [v11,21/21] eal: allow lcore remap dpdklab
2025-10-09 13:33 ` |SUCCESS| " dpdklab
2025-10-09 13:34 ` |PENDING| " dpdklab
2025-10-09 13:37 ` |SUCCESS| " dpdklab
2025-10-09 13:41 ` |PENDING| " dpdklab
2025-10-09 13:50 ` |SUCCESS| " dpdklab
2025-10-09 13:50 ` |PENDING| " dpdklab
2025-10-09 13:52 ` |SUCCESS| " dpdklab
2025-10-09 13:54 ` dpdklab
2025-10-09 13:58 ` dpdklab
2025-10-09 13:59 ` dpdklab
2025-10-09 14:12 ` dpdklab
2025-10-09 14:15 ` dpdklab
2025-10-09 14:17 ` dpdklab
2025-10-09 14:22 ` dpdklab
2025-10-09 14:59 ` |SUCCESS| pw157390 [PATCH v11 21/21] eal: allow lcore remapping with autodetected core affinity 0-day Robot
2025-10-09 14:59 ` 0-day Robot [this message]
2025-10-09 19:59 ` |WARNING| pw157370-157390 [PATCH] [v11,21/21] eal: allow lcore remap dpdklab
2025-10-09 20:44 ` dpdklab
2025-10-09 20:45 ` |PENDING| " 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=20251009145943.2968049-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).