From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw103351 [PATCH] crypto/mlx5: support 1MB data-unit
Date: Mon, 1 Nov 2021 11:48:42 -0400 (EDT) [thread overview]
Message-ID: <20211101154842.D619260524@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
Test-Label: iol-spell-check-testing
Test-Status: SUCCESS
http://dpdk.org/patch/103351
_Testing PASS_
Submitter: Raja Zidane <rzidane@nvidia.com>
Date: Monday, November 01 2021 15:05:47
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6cc51b1293ceac4a77d4bf7ac91a8bbd59e1f78c
103351 --> testing pass
Test environment and result as below:
+--------------+-------------+
| Environment | spell_check |
+==============+=============+
| Ubuntu 20.04 | PASS |
+--------------+-------------+
==== 20 line log output for Ubuntu 20.04 (spell_check): ====
Errors found: 0
==== End log output ====
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/19887/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-11-01 15:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 15:48 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-01 19:57 dpdklab
2021-11-01 19:39 dpdklab
2021-11-01 16:18 dpdklab
2021-11-01 16:09 dpdklab
2021-11-01 16:00 dpdklab
2021-11-01 16:00 dpdklab
2021-11-01 15:58 dpdklab
2021-11-01 15:56 dpdklab
2021-11-01 15:49 dpdklab
2021-11-01 15:46 dpdklab
2021-11-01 15:43 dpdklab
[not found] <20211101150547.34040-1-rzidane@nvidia.com>
2021-11-01 15:07 ` checkpatch
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=20211101154842.D619260524@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@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).