From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw154952 [PATCH] net/mlx5: fix inline data size adjustment
Date: Wed, 02 Jul 2025 10:37:35 -0700 (PDT) [thread overview]
Message-ID: <68656e5f.170a0220.a8469.8d6aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250702093459.102142-1-shperetz@nvidia.com>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/154952
_Testing PASS_
Submitter: Shani Peretz <shperetz@nvidia.com>
Date: Wednesday, July 02 2025 09:34:59
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:5c0c1a13c34aa57c6e18f9ba852a9b5807c58b72
154952 --> testing pass
Upstream job id: Generic-VM-DPDK-Compile-Meson#36881
Test environment and result as below:
+--------------+--------------------+
| Environment | dpdk_meson_compile |
+==============+====================+
| Ubuntu 20.04 | PASS |
+--------------+--------------------+
Ubuntu 20.04
Kernel: 4.19
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33564/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2025-07-02 17:37 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250702093459.102142-1-shperetz@nvidia.com>
2025-07-02 9:01 ` |SUCCESS| pw154952 [PATCH] net/mlx5: fix inline data size adjustment for Verbs API qemudev
2025-07-02 9:05 ` qemudev
2025-07-02 9:34 ` checkpatch
2025-07-02 10:43 ` 0-day Robot
2025-07-02 17:26 ` |SUCCESS| pw154952 [PATCH] net/mlx5: fix inline data size adjustment dpdklab
2025-07-02 17:37 ` dpdklab [this message]
2025-07-02 17:51 ` dpdklab
2025-07-02 18:27 ` |PENDING| " dpdklab
2025-07-02 18:59 ` |SUCCESS| " dpdklab
2025-07-02 19:40 ` dpdklab
2025-07-02 20:01 ` |PENDING| " dpdklab
2025-07-02 20:38 ` |SUCCESS| " dpdklab
2025-07-02 20:38 ` dpdklab
2025-07-02 21:03 ` dpdklab
2025-07-02 21:11 ` dpdklab
2025-07-02 21:40 ` dpdklab
2025-07-04 16:47 ` |PENDING| " dpdklab
2025-07-04 16:51 ` dpdklab
2025-07-04 16:52 ` dpdklab
2025-07-04 16:53 ` dpdklab
2025-07-04 17:02 ` |SUCCESS| " dpdklab
2025-07-04 17:08 ` |PENDING| " dpdklab
2025-07-04 17:14 ` |SUCCESS| " dpdklab
2025-07-04 17:25 ` dpdklab
2025-07-04 17:43 ` dpdklab
2025-07-04 17:43 ` dpdklab
2025-07-04 17:44 ` dpdklab
2025-07-04 17:44 ` dpdklab
2025-07-04 17:44 ` dpdklab
2025-07-04 17:44 ` dpdklab
2025-07-04 17:59 ` dpdklab
2025-07-04 17:59 ` dpdklab
2025-07-04 18:06 ` dpdklab
2025-07-04 18:17 ` |WARNING| " 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=68656e5f.170a0220.a8469.8d6aSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).