From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136833 [PATCH] net/ixgbevf: fix RSS init for x550 nics
Date: Thu, 15 Feb 2024 11:36:43 -0800 (PST) [thread overview]
Message-ID: <65ce67cb.0c0a0220.12dc3.13f9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136833
_Testing PASS_
Submitter: None <edwin.brossette@6wind.com>
Date: Thursday, February 15 2024 13:31:45
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4e7732d6c4c64514dc26c3cc0203d19851b5f5aa
136833 --> testing pass
Test environment and result as below:
+----------------------+--------------------+
| Environment | dpdk_meson_compile |
+======================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------+--------------------+
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/29161/
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-15 19:36 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 19:36 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-15 21:11 dpdklab
2024-02-15 21:04 dpdklab
2024-02-15 21:02 dpdklab
2024-02-15 21:01 dpdklab
2024-02-15 21:01 dpdklab
2024-02-15 20:57 dpdklab
2024-02-15 20:55 dpdklab
2024-02-15 20:54 dpdklab
2024-02-15 20:54 dpdklab
2024-02-15 20:53 dpdklab
2024-02-15 20:46 dpdklab
2024-02-15 20:45 dpdklab
2024-02-15 20:44 dpdklab
2024-02-15 20:44 dpdklab
2024-02-15 20:43 dpdklab
2024-02-15 20:41 dpdklab
2024-02-15 20:40 dpdklab
2024-02-15 20:34 dpdklab
2024-02-15 20:34 dpdklab
2024-02-15 20:26 dpdklab
2024-02-15 20:26 dpdklab
2024-02-15 20:20 dpdklab
2024-02-15 20:19 dpdklab
2024-02-15 20:19 dpdklab
2024-02-15 20:19 dpdklab
2024-02-15 20:18 dpdklab
2024-02-15 20:14 dpdklab
2024-02-15 20:14 dpdklab
2024-02-15 20:11 dpdklab
2024-02-15 20:11 dpdklab
2024-02-15 20:10 dpdklab
2024-02-15 20:09 dpdklab
2024-02-15 20:09 dpdklab
2024-02-15 20:09 dpdklab
2024-02-15 20:09 dpdklab
2024-02-15 20:08 dpdklab
2024-02-15 20:08 dpdklab
2024-02-15 20:06 dpdklab
2024-02-15 20:05 dpdklab
2024-02-15 20:04 dpdklab
2024-02-15 20:04 dpdklab
2024-02-15 20:04 dpdklab
2024-02-15 20:00 dpdklab
2024-02-15 19:58 dpdklab
2024-02-15 19:55 dpdklab
2024-02-15 19:55 dpdklab
2024-02-15 19:54 dpdklab
2024-02-15 19:53 dpdklab
2024-02-15 19:52 dpdklab
2024-02-15 19:52 dpdklab
2024-02-15 19:51 dpdklab
2024-02-15 19:51 dpdklab
2024-02-15 19:48 dpdklab
2024-02-15 19:47 dpdklab
2024-02-15 19:45 dpdklab
2024-02-15 19:44 dpdklab
2024-02-15 19:44 dpdklab
2024-02-15 19:44 dpdklab
2024-02-15 19:37 dpdklab
2024-02-15 19:37 dpdklab
2024-02-15 19:35 dpdklab
2024-02-15 19:35 dpdklab
2024-02-15 19:34 dpdklab
2024-02-15 19:34 dpdklab
2024-02-15 19:33 dpdklab
2024-02-15 19:32 dpdklab
2024-02-15 19:31 dpdklab
2024-02-15 19:31 dpdklab
2024-02-15 19:23 dpdklab
2024-02-15 19:20 dpdklab
[not found] <20240215133145.181302-1-edwin.brossette@6wind.com>
2024-02-15 13:08 ` qemudev
2024-02-15 13:13 ` qemudev
2024-02-15 13:33 ` checkpatch
2024-02-15 14: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=65ce67cb.0c0a0220.12dc3.13f9SMTPIN_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).