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| pw123361 [PATCH V4] pipeline: add RSS support
Date: Tue,  7 Feb 2023 14:19:28 -0500	[thread overview]
Message-ID: <20230207191928.1266038-1-robot@bytheb.org> (raw)
In-Reply-To: <20230207164145.652805-1-cristian.dumitrescu@intel.com>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2023-02-07 19:20 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230207164145.652805-1-cristian.dumitrescu@intel.com>
2023-02-07 16:34 ` qemudev
2023-02-07 16:38 ` qemudev
2023-02-07 16:43 ` |WARNING| " checkpatch
2023-02-07 19:19 ` 0-day Robot [this message]
2023-02-07 17:11 |SUCCESS| pw123361 [PATCH] [V4] " dpdklab
2023-02-07 17:26 dpdklab
2023-02-07 17:34 dpdklab
2023-02-07 17:38 dpdklab
2023-02-07 17:47 dpdklab
2023-02-07 18:06 dpdklab
2023-02-07 18:13 dpdklab
2023-02-07 18:20 dpdklab
2023-02-07 18:39 dpdklab
2023-02-07 20:04 dpdklab
2023-02-07 20:32 dpdklab
2023-02-07 20:37 dpdklab
2023-02-08 16:32 dpdklab
2023-02-08 17:02 dpdklab
2023-02-08 17:28 dpdklab
2023-02-08 17:28 dpdklab
2023-02-08 17:28 dpdklab
2023-02-08 17:31 dpdklab
2023-02-08 17:37 dpdklab
2023-02-09  4:46 dpdklab
2023-02-09  8:57 dpdklab
2023-02-12 18:20 dpdklab
2023-02-12 18:37 dpdklab
2023-02-12 18:39 dpdklab
2023-02-12 18:42 dpdklab
2023-02-12 18:43 dpdklab
2023-02-12 18:44 dpdklab
2023-02-12 18:45 dpdklab
2023-02-12 18:46 dpdklab
2023-02-12 18:47 dpdklab
2023-02-12 18:49 dpdklab
2023-02-12 18:50 dpdklab
2023-02-12 18:50 dpdklab
2023-02-12 21:50 dpdklab
2023-02-16 15:35 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=20230207191928.1266038-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).