From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw104180 [PATCH] failsafe: Bug fix for the secondary process to support RX-TX
Date: Thu, 11 Nov 2021 05:38:33 -0500 [thread overview]
Message-ID: <20211111103833.25449-1-robot@bytheb.org> (raw)
In-Reply-To: <20211111100221.84621-1-kumaraparamesh92@gmail.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/104180/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/1448314183
next prev parent reply other threads:[~2021-11-11 10:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211111100221.84621-1-kumaraparamesh92@gmail.com>
2021-11-11 10:03 ` |WARNING| " checkpatch
2021-11-11 10:38 ` 0-day Robot [this message]
2021-11-11 11:02 |SUCCESS| " dpdklab
2021-11-11 11:03 dpdklab
2021-11-11 11:05 dpdklab
2021-11-11 11:12 dpdklab
2021-11-11 11:17 dpdklab
2021-11-11 11:18 dpdklab
2021-11-11 11:21 dpdklab
2021-11-11 11:36 dpdklab
2021-11-11 11:57 dpdklab
2021-11-11 12:16 dpdklab
2021-11-11 12:17 dpdklab
2021-11-11 15:07 dpdklab
2021-11-11 15:25 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=20211111103833.25449-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).