From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw125229 [PATCH v2] bus/auxiliary: support cleanup callback
Date: Fri, 17 Mar 2023 13:59:22 -0400 [thread overview]
Message-ID: <20230317175922.382515-1-robot@bytheb.org> (raw)
In-Reply-To: <20230317152447.4570-1-xuemingl@nvidia.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/125229/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/4449182561
next prev parent reply other threads:[~2023-03-17 16:59 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230317152447.4570-1-xuemingl@nvidia.com>
2023-03-17 15:14 ` qemudev
2023-03-17 15:18 ` qemudev
2023-03-17 15:26 ` checkpatch
2023-03-17 17:59 ` 0-day Robot [this message]
2023-03-17 16:00 |SUCCESS| pw125229 [PATCH] [v2] " dpdklab
2023-03-17 16:06 dpdklab
2023-03-17 16:09 dpdklab
2023-03-17 16:12 dpdklab
2023-03-17 16:15 dpdklab
2023-03-17 16:23 dpdklab
2023-03-17 16:26 dpdklab
2023-03-17 16:31 dpdklab
2023-03-17 16:36 dpdklab
2023-03-17 16:37 dpdklab
2023-03-17 16:51 dpdklab
2023-03-17 16:51 dpdklab
2023-03-17 16:58 dpdklab
2023-03-17 16:58 dpdklab
2023-03-17 17:03 dpdklab
2023-03-17 17:05 dpdklab
2023-03-17 17:10 dpdklab
2023-03-17 17:20 dpdklab
2023-03-17 17:23 dpdklab
2023-03-17 17:25 dpdklab
2023-03-17 17:35 dpdklab
2023-03-17 17:38 dpdklab
2023-03-17 17:43 dpdklab
2023-03-17 17:45 dpdklab
2023-03-17 17:48 dpdklab
2023-03-17 17:51 dpdklab
2023-03-17 17:57 dpdklab
2023-03-17 18:10 dpdklab
2023-03-17 18:39 dpdklab
2023-03-17 18:47 dpdklab
2023-03-19 11:20 dpdklab
2023-03-19 12:56 dpdklab
2023-03-19 21:59 dpdklab
2023-03-20 0:50 dpdklab
2023-03-20 15:09 dpdklab
2023-03-20 19:24 dpdklab
2023-03-21 9:22 dpdklab
2023-03-21 21:09 dpdklab
2023-03-21 23:05 dpdklab
2023-03-24 0:16 dpdklab
2023-03-24 0:17 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=20230317175922.382515-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).