From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136646 [PATCH] drivers: use common container_of macro
Date: Tue, 13 Feb 2024 14:24:42 -0800 (PST) [thread overview]
Message-ID: <65cbec2a.020a0220.e477f.0259SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136646
_Testing PASS_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Tuesday, February 13 2024 15:37:41
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4cf59bbc9edf5419a9f2644a132c9a96c071a4c8
136646 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| FreeBSD 13.2 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29134/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-13 22:24 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 22:24 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-14 2:37 dpdklab
2024-02-14 0:35 dpdklab
2024-02-14 0:06 dpdklab
2024-02-13 23:42 dpdklab
2024-02-13 23:40 dpdklab
2024-02-13 23:40 dpdklab
2024-02-13 23:37 dpdklab
2024-02-13 23:36 dpdklab
2024-02-13 23:36 dpdklab
2024-02-13 23:36 dpdklab
2024-02-13 23:35 dpdklab
2024-02-13 23:35 dpdklab
2024-02-13 23:28 dpdklab
2024-02-13 23:24 dpdklab
2024-02-13 23:24 dpdklab
2024-02-13 23:23 dpdklab
2024-02-13 23:21 dpdklab
2024-02-13 23:21 dpdklab
2024-02-13 23:19 dpdklab
2024-02-13 23:19 dpdklab
2024-02-13 23:19 dpdklab
2024-02-13 23:19 dpdklab
2024-02-13 23:19 dpdklab
2024-02-13 23:17 dpdklab
2024-02-13 23:16 dpdklab
2024-02-13 23:14 dpdklab
2024-02-13 23:14 dpdklab
2024-02-13 23:14 dpdklab
2024-02-13 23:11 dpdklab
2024-02-13 23:10 dpdklab
2024-02-13 23:08 dpdklab
2024-02-13 23:07 dpdklab
2024-02-13 23:01 dpdklab
2024-02-13 23:01 dpdklab
2024-02-13 22:59 dpdklab
2024-02-13 22:57 dpdklab
2024-02-13 22:57 dpdklab
2024-02-13 22:54 dpdklab
2024-02-13 22:52 dpdklab
2024-02-13 22:52 dpdklab
2024-02-13 22:52 dpdklab
2024-02-13 22:50 dpdklab
2024-02-13 22:45 dpdklab
2024-02-13 22:44 dpdklab
2024-02-13 22:34 dpdklab
2024-02-13 22:33 dpdklab
2024-02-13 22:29 dpdklab
2024-02-13 22:29 dpdklab
2024-02-13 22:29 dpdklab
2024-02-13 22:28 dpdklab
2024-02-13 22:28 dpdklab
2024-02-13 22:27 dpdklab
2024-02-13 22:27 dpdklab
2024-02-13 22:26 dpdklab
2024-02-13 22:26 dpdklab
2024-02-13 22:26 dpdklab
2024-02-13 22:25 dpdklab
2024-02-13 22:22 dpdklab
2024-02-13 22:21 dpdklab
2024-02-13 22:21 dpdklab
2024-02-13 22:20 dpdklab
2024-02-13 22:19 dpdklab
2024-02-13 22:10 dpdklab
2024-02-13 22:04 dpdklab
2024-02-13 22:01 dpdklab
2024-02-13 21:51 dpdklab
2024-02-13 21:51 dpdklab
2024-02-13 17:53 dpdklab
2024-02-13 17:52 dpdklab
[not found] <20240213153741.2133915-1-david.marchand@redhat.com>
2024-02-13 15:15 ` qemudev
2024-02-13 15:19 ` qemudev
2024-02-13 15:38 ` checkpatch
2024-02-13 16:24 ` 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=65cbec2a.020a0220.e477f.0259SMTPIN_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).