From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw143625 [PATCH 4/4] dmadev: clean code for verify parameter
Date: Thu, 5 Sep 2024 03:44:28 -0400 [thread overview]
Message-ID: <20240905074428.3201532-1-robot@bytheb.org> (raw)
In-Reply-To: <20240905064638.17980-5-haijie1@huawei.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/143625/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/10715542898
next prev parent reply other threads:[~2024-09-05 7:44 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240905064638.17980-5-haijie1@huawei.com>
2024-09-05 6:46 ` |SUCCESS| pw143622-143625 " qemudev
2024-09-05 6:51 ` qemudev
2024-09-05 6:57 ` |SUCCESS| pw143625 " checkpatch
2024-09-05 7:44 ` 0-day Robot [this message]
2024-09-05 17:02 ` |PENDING| pw143622-143625 [PATCH] [4/4] dmadev: clean code for verif dpdklab
2024-09-05 17:11 ` |SUCCESS| " dpdklab
2024-09-05 17:11 ` dpdklab
2024-09-05 17:14 ` dpdklab
2024-09-05 17:15 ` dpdklab
2024-09-05 17:16 ` dpdklab
2024-09-05 17:17 ` dpdklab
2024-09-05 17:19 ` dpdklab
2024-09-05 17:19 ` dpdklab
2024-09-05 17:19 ` dpdklab
2024-09-05 17:20 ` dpdklab
2024-09-05 17:21 ` dpdklab
2024-09-05 17:27 ` |PENDING| " dpdklab
2024-09-05 19:24 ` |SUCCESS| " dpdklab
2024-09-05 19:24 ` dpdklab
2024-09-05 19:26 ` dpdklab
2024-09-05 19:31 ` dpdklab
2024-09-05 19:32 ` dpdklab
2024-09-05 19:35 ` dpdklab
2024-09-05 19:39 ` dpdklab
2024-09-05 19:39 ` dpdklab
2024-09-05 22:19 ` dpdklab
2024-09-05 22:21 ` dpdklab
2024-09-05 22:24 ` dpdklab
2024-09-05 22:24 ` dpdklab
2024-09-05 22:26 ` dpdklab
2024-09-05 22:29 ` dpdklab
2024-09-07 1:38 ` dpdklab
2024-09-17 23:48 ` dpdklab
2024-09-18 0:08 ` 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=20240905074428.3201532-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).