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| pw106236 [PATCH v2] devtools/cocci: update cocci for ethdev namespace
Date: Sun, 23 Jan 2022 14:19:30 -0500	[thread overview]
Message-ID: <20220123191930.26349-1-robot@bytheb.org> (raw)
In-Reply-To: <20220123172046.1296964-1-aman.deep.singh@intel.com>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2022-01-23 18:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220123172046.1296964-1-aman.deep.singh@intel.com>
2022-01-23 17:39 ` |WARNING| " checkpatch
2022-01-23 19:19 ` 0-day Robot [this message]
2022-01-23 18:56 |SUCCESS| pw106236 [PATCH] [v2] " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2022-01-23 18:49 dpdklab
2022-01-23 18:48 dpdklab
2022-01-23 18:45 dpdklab
2022-01-23 18:43 dpdklab
2022-01-23 18:25 dpdklab
2022-01-23 18:23 dpdklab
2022-01-23 18:20 dpdklab
2022-01-23 18:19 dpdklab
2022-01-23 18:19 dpdklab
2022-01-23 18:15 dpdklab
2022-01-23 18:12 dpdklab
2022-01-23 18:10 dpdklab
2022-01-23 18:06 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=20220123191930.26349-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).