From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw102857 [PATCH] net/bnxt: refactor Rx ring cleanup for representors
Date: Thu, 28 Oct 2021 01:20:33 -0400 (EDT) [thread overview]
Message-ID: <20211028052033.D225B60524@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 845 bytes --]
Test-Label: iol-aarch64-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/102857
_Testing PASS_
Submitter: Ajit Khaparde <ajit.khaparde@broadcom.com>
Date: Tuesday, October 26 2021 05:14:55
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6c390cee976e33b1e9d8562d32c9d3ebe5d9ce94
102857 --> testing pass
Test environment and result as below:
+------------------+----------------+
| Environment | dpdk_unit_test |
+==================+================+
| Ubuntu 20.04 ARM | PASS |
+------------------+----------------+
Ubuntu 20.04 ARM
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/19708/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-10-28 5:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 5:20 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-27 0:13 dpdklab
2021-10-26 19:26 dpdklab
2021-10-26 19:12 dpdklab
2021-10-26 8:46 dpdklab
2021-10-26 8:30 dpdklab
2021-10-26 8:04 dpdklab
2021-10-26 6:20 dpdklab
2021-10-26 6:18 dpdklab
2021-10-26 5:57 dpdklab
2021-10-26 5:55 dpdklab
2021-10-26 5:53 dpdklab
2021-10-26 5:49 dpdklab
2021-10-26 5:41 dpdklab
2021-10-26 5:40 dpdklab
[not found] <20211026051455.84103-1-ajit.khaparde@broadcom.com>
2021-10-26 5:15 ` 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=20211028052033.D225B60524@noxus.dpdklab.iol.unh.edu \
--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).