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| pw123689 [PATCH v5] net/af_xdp: support CNI Integration
Date: Mon, 13 Feb 2023 16:20:58 -0500	[thread overview]
Message-ID: <20230213212058.3052208-1-robot@bytheb.org> (raw)
In-Reply-To: <20230210154828.397475-1-shibin.koikkara.reeny@intel.com>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2023-02-13 20:21 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230210154828.397475-1-shibin.koikkara.reeny@intel.com>
2023-02-10 15:38 ` qemudev
2023-02-10 15:42 ` qemudev
2023-02-10 15:49 ` |WARNING| " checkpatch
2023-02-13 21:20 ` 0-day Robot [this message]
2023-02-15 11:06 |SUCCESS| pw123689 [PATCH] [v5] " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-02-13 22:26 dpdklab
2023-02-12 22:13 dpdklab
2023-02-12  4:22 dpdklab
2023-02-12  4:22 dpdklab
2023-02-12  4:20 dpdklab
2023-02-12  4:17 dpdklab
2023-02-12  4:15 dpdklab
2023-02-12  4:14 dpdklab
2023-02-12  4:12 dpdklab
2023-02-12  4:10 dpdklab
2023-02-12  4:09 dpdklab
2023-02-12  4:07 dpdklab
2023-02-12  4:04 dpdklab
2023-02-12  4:03 dpdklab
2023-02-12  4:02 dpdklab
2023-02-12  3:15 dpdklab
2023-02-10 18:06 dpdklab
2023-02-10 16:42 dpdklab
2023-02-10 16:40 dpdklab
2023-02-10 16:36 dpdklab
2023-02-10 16:33 dpdklab
2023-02-10 16:32 dpdklab
2023-02-10 16:30 dpdklab
2023-02-10 16:29 dpdklab
2023-02-10 16:27 dpdklab
2023-02-10 16:21 dpdklab
2023-02-10 16:21 dpdklab
2023-02-10 16:20 dpdklab
2023-02-10 16:18 dpdklab
2023-02-10 16:17 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=20230213212058.3052208-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).