From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw104519 [PATCH v2] common/mlx5: fix mempool registration
Date: Thu, 18 Nov 2021 11:18:08 -0500 [thread overview]
Message-ID: <20211118161808.22727-1-robot@bytheb.org> (raw)
In-Reply-To: <20211118152501.2936413-1-dkozlyuk@nvidia.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/104519/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/1477161630
next prev parent reply other threads:[~2021-11-18 16:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211118152501.2936413-1-dkozlyuk@nvidia.com>
2021-11-18 15:26 ` |WARNING| " checkpatch
2021-11-18 16:18 ` 0-day Robot [this message]
2021-11-19 5:47 |SUCCESS| pw104519 [PATCH] [v2] " dpdklab
2021-11-19 6:05 dpdklab
2021-11-19 6:06 dpdklab
2021-11-19 6:10 dpdklab
2021-11-19 6:15 dpdklab
2021-11-19 6:22 dpdklab
2021-11-19 6:25 dpdklab
2021-11-19 6:28 dpdklab
2021-11-19 6:40 dpdklab
2021-11-19 6:58 dpdklab
2021-11-19 8:20 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=20211118161808.22727-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).