From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw130772 [PATCH] net/mlx5: fix jump ipool entry size
Date: Fri, 25 Aug 2023 15:59:15 -0400 [thread overview]
Message-ID: <20230825195915.2628753-1-robot@bytheb.org> (raw)
In-Reply-To: <20230825184330.3334318-1-dsosnowski@nvidia.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/130772/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/5979485921
next prev parent reply other threads:[~2023-08-25 19:59 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230825184330.3334318-1-dsosnowski@nvidia.com>
2023-08-25 18:40 ` qemudev
2023-08-25 18:44 ` qemudev
2023-08-25 18:44 ` checkpatch
2023-08-25 19:59 ` 0-day Robot [this message]
2023-08-26 0:50 dpdklab
2023-08-26 0:50 dpdklab
2023-08-26 0:57 dpdklab
2023-08-26 0:58 dpdklab
2023-08-26 0:58 dpdklab
2023-08-26 0:59 dpdklab
2023-08-26 1:18 dpdklab
2023-08-26 1:19 dpdklab
2023-08-26 1:19 dpdklab
2023-08-26 1:19 dpdklab
2023-08-26 1:19 dpdklab
2023-08-26 1:20 dpdklab
2023-08-26 1:20 dpdklab
2023-08-26 1:20 dpdklab
2023-08-26 1:20 dpdklab
2023-08-26 1:20 dpdklab
2023-08-26 1:20 dpdklab
2023-08-26 1:21 dpdklab
2023-08-26 1:21 dpdklab
2023-08-26 1:21 dpdklab
2023-08-26 1:21 dpdklab
2023-08-26 1:21 dpdklab
2023-08-26 1:21 dpdklab
2023-08-26 1:21 dpdklab
2023-08-26 1:21 dpdklab
2023-08-26 1:21 dpdklab
2023-08-26 1:21 dpdklab
2023-08-26 1:22 dpdklab
2023-08-26 1:22 dpdklab
2023-08-26 1:22 dpdklab
2023-08-26 1:22 dpdklab
2023-08-26 1:22 dpdklab
2023-08-26 1:22 dpdklab
2023-08-26 1:24 dpdklab
2023-08-26 1:26 dpdklab
2023-08-26 1:27 dpdklab
2023-08-26 1:28 dpdklab
2023-08-26 1:28 dpdklab
2023-08-26 1:35 dpdklab
2023-08-26 1:37 dpdklab
2023-08-26 1:52 dpdklab
2023-08-26 1:52 dpdklab
2023-08-26 2:36 dpdklab
2023-08-26 2:54 dpdklab
2023-08-26 3:05 dpdklab
2023-08-26 3:09 dpdklab
2023-08-26 3:14 dpdklab
2023-08-26 3:19 dpdklab
2023-08-26 3:37 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=20230825195915.2628753-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).