From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw103510 [PATCH] doc: remove deprecation notices for eventdev
Date: Tue, 2 Nov 2021 13:09:13 -0400 (EDT) [thread overview]
Message-ID: <20211102170913.21FC760524@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 942 bytes --]
Test-Label: iol-spell-check-testing
Test-Status: SUCCESS
http://dpdk.org/patch/103510
_Testing PASS_
Submitter: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Date: Tuesday, November 02 2021 15:49:56
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b2be63b55ab086c52c082d5c0b2b01fffbc48326
103510 --> 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/19933/
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-02 17:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 17:09 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-03 16:59 dpdklab
2021-11-03 9:42 dpdklab
2021-11-03 8:11 dpdklab
2021-11-03 7:59 dpdklab
2021-11-03 7:42 dpdklab
2021-11-02 22:21 dpdklab
2021-11-02 22:11 dpdklab
2021-11-02 21:53 dpdklab
2021-11-02 21:30 dpdklab
2021-11-02 21:13 dpdklab
2021-11-02 21:05 dpdklab
2021-11-02 20:54 dpdklab
2021-11-02 17:55 dpdklab
[not found] <20211102154956.1443591-1-jerinj@marvell.com>
2021-11-02 15:53 ` 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=20211102170913.21FC760524@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).