From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130870 [PATCH] vhost: avoid potential null pointer acces
Date: Wed, 30 Aug 2023 05:12:27 -0700 (PDT) [thread overview]
Message-ID: <64ef322b.170a0220.77a48.471eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/130870
_Functional Testing PASS_
Submitter: Li Feng <fengli@smartx.com>
Date: Wednesday, August 30 2023 08:47:08
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b7b8de26f34d39c8aaded44d8a468da5e68f19da
130870 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27469/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-30 12:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 12:12 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-30 16:35 dpdklab
2023-08-30 16:31 dpdklab
2023-08-30 16:13 dpdklab
2023-08-30 15:50 dpdklab
2023-08-30 15:34 dpdklab
2023-08-30 12:57 dpdklab
2023-08-30 12:53 dpdklab
2023-08-30 12:45 dpdklab
2023-08-30 12:44 dpdklab
2023-08-30 12:30 dpdklab
2023-08-30 12:18 dpdklab
2023-08-30 12:17 dpdklab
2023-08-30 12:15 dpdklab
2023-08-30 12:08 dpdklab
2023-08-30 12:02 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=64ef322b.170a0220.77a48.471eSMTPIN_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).