From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132636 [PATCH] event/sw: fix missing device pointer
Date: Mon, 16 Oct 2023 13:41:59 -0700 (PDT) [thread overview]
Message-ID: <652da017.050a0220.3d673.0205SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132636
_Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Monday, October 16 2023 15:17:13
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:441e777b85f1ea1eb6a2a970ff5d5c8e027f520c
132636 --> testing pass
Test environment and result as below:
+----------------------+------------------------------+---------------------------+--------------+
| Environment | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest | lpm_autotest |
+======================+==============================+===========================+==============+
| Debian 11 (arm) | PASS | PASS | SKIPPED |
+----------------------+------------------------------+---------------------------+--------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | SKIPPED | PASS |
+----------------------+------------------------------+---------------------------+--------------+
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27944/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-16 20:42 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 20:41 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-18 21:04 dpdklab
2023-10-18 0:42 dpdklab
2023-10-18 0:15 dpdklab
2023-10-17 0:19 dpdklab
2023-10-16 21:45 dpdklab
2023-10-16 21:08 dpdklab
2023-10-16 20:43 dpdklab
2023-10-16 20:42 dpdklab
2023-10-16 20:42 dpdklab
2023-10-16 20:40 dpdklab
2023-10-16 20:38 dpdklab
2023-10-16 20:37 dpdklab
2023-10-16 20:36 dpdklab
2023-10-16 20:36 dpdklab
2023-10-16 20:36 dpdklab
2023-10-16 20:35 dpdklab
2023-10-16 20:35 dpdklab
2023-10-16 20:35 dpdklab
2023-10-16 20:34 dpdklab
2023-10-16 20:34 dpdklab
2023-10-16 20:34 dpdklab
2023-10-16 20:34 dpdklab
2023-10-16 20:33 dpdklab
2023-10-16 20:33 dpdklab
2023-10-16 20:33 dpdklab
2023-10-16 20:32 dpdklab
2023-10-16 20:31 dpdklab
2023-10-16 20:30 dpdklab
2023-10-16 20:30 dpdklab
2023-10-16 20:30 dpdklab
2023-10-16 20:29 dpdklab
2023-10-16 20:29 dpdklab
2023-10-16 20:29 dpdklab
2023-10-16 20:29 dpdklab
2023-10-16 20:28 dpdklab
2023-10-16 20:27 dpdklab
2023-10-16 20:27 dpdklab
2023-10-16 20:26 dpdklab
2023-10-16 20:17 dpdklab
2023-10-16 20:16 dpdklab
2023-10-16 20:15 dpdklab
2023-10-16 20:10 dpdklab
2023-10-16 19:59 dpdklab
[not found] <20231016151713.711965-1-bruce.richardson@intel.com>
2023-10-16 14:58 ` qemudev
2023-10-16 15:02 ` qemudev
2023-10-16 16:19 ` 0-day Robot
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=652da017.050a0220.3d673.0205SMTPIN_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).