From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw125195 [PATCH] app/testpmd: revert cleanup cleanly from signal
Date: Thu, 16 Mar 2023 16:01:04 -0400 [thread overview]
Message-ID: <20230316200104.40237-1-robot@bytheb.org> (raw)
In-Reply-To: <20230316172739.77933-1-ferruh.yigit@amd.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/125195/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/4440042402
next prev parent reply other threads:[~2023-03-16 19:01 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230316172739.77933-1-ferruh.yigit@amd.com>
2023-03-16 17:22 ` qemudev
2023-03-16 17:26 ` qemudev
2023-03-16 17:28 ` |WARNING| " checkpatch
2023-03-16 20:01 ` 0-day Robot [this message]
2023-03-18 22:12 |SUCCESS| " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-03-18 22:05 dpdklab
2023-03-18 21:58 dpdklab
2023-03-18 20:59 dpdklab
2023-03-17 17:09 dpdklab
2023-03-17 17:04 dpdklab
2023-03-16 23:40 dpdklab
2023-03-16 23:19 dpdklab
2023-03-16 22:08 dpdklab
2023-03-16 21:37 dpdklab
2023-03-16 21:28 dpdklab
2023-03-16 21:15 dpdklab
2023-03-16 20:21 dpdklab
2023-03-16 20:16 dpdklab
2023-03-16 20:08 dpdklab
2023-03-16 20:03 dpdklab
2023-03-16 19:42 dpdklab
2023-03-16 19:37 dpdklab
2023-03-16 19:33 dpdklab
2023-03-16 19:30 dpdklab
2023-03-16 19:17 dpdklab
2023-03-16 19:16 dpdklab
2023-03-16 19:06 dpdklab
2023-03-16 19:04 dpdklab
2023-03-16 19:00 dpdklab
2023-03-16 18:54 dpdklab
2023-03-16 18:53 dpdklab
2023-03-16 18:48 dpdklab
2023-03-16 18:48 dpdklab
2023-03-16 18:48 dpdklab
2023-03-16 18:43 dpdklab
2023-03-16 18:37 dpdklab
2023-03-16 18:34 dpdklab
2023-03-16 18:32 dpdklab
2023-03-16 18:31 dpdklab
2023-03-16 18:24 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=20230316200104.40237-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).