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| pw128874 [PATCH v7 1/1] hash: add XOR32 hash function
Date: Tue, 20 Jun 2023 15:59:31 -0400	[thread overview]
Message-ID: <20230620195931.3345727-1-robot@bytheb.org> (raw)
In-Reply-To: <20230620191253.3218830-1-qobilidop@gmail.com>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2023-06-20 19:59 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230620191253.3218830-1-qobilidop@gmail.com>
2023-06-20 19:13 ` checkpatch
2023-06-20 19:59 ` 0-day Robot [this message]
2023-06-21  0:26 ` qemudev
2023-06-21  0:27 ` qemudev
2023-06-21  0:39 ` qemudev
2023-06-21  0:40 ` qemudev
2023-06-21 13:46 |SUCCESS| pw128874 [PATCH] [v7,1/1] " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-06-21 13:46 dpdklab
2023-06-21 13:39 dpdklab
2023-06-21  9:43 dpdklab
2023-06-21  9:20 dpdklab
2023-06-21  9:14 dpdklab
2023-06-21  9:09 dpdklab
2023-06-21  4:55 dpdklab
2023-06-21  4:31 dpdklab
2023-06-20 20:31 dpdklab
2023-06-20 20:31 dpdklab
2023-06-20 20:27 dpdklab
2023-06-20 20:22 dpdklab
2023-06-20 20:18 dpdklab
2023-06-20 20:12 dpdklab
2023-06-20 20:10 dpdklab
2023-06-20 20:08 dpdklab
2023-06-20 20:08 dpdklab
2023-06-20 20:04 dpdklab
2023-06-20 19:58 dpdklab
2023-06-20 19:52 dpdklab
2023-06-20 19:51 dpdklab
2023-06-20 19:50 dpdklab
2023-06-20 19:50 dpdklab
2023-06-20 19:50 dpdklab
2023-06-20 19:49 dpdklab
2023-06-20 19:49 dpdklab
2023-06-20 19:49 dpdklab
2023-06-20 19:49 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=20230620195931.3345727-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).