From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Tomer Shmilovich <tshmilovich@nvidia.com>,
dpdk-test-reports@iol.unh.edu,
Tomer Shmilovich <tshmilovich@nvidia.com>
Subject: |WARNING| pw131971 [PATCH] net/mlx5: supporting group set miss actio
Date: Tue, 26 Sep 2023 14:47:51 -0700 (PDT) [thread overview]
Message-ID: <65135187.170a0220.d2f65.9109SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: WARNING
http://dpdk.org/patch/131971
_Testing issues_
Submitter: Tomer Shmilovich <tshmilovich@nvidia.com>
Date: Tuesday, September 26 2023 15:58:35
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:d58c97481a136ad5342c9d8717b22bdaa5eccd43
131971 --> testing fail
Test environment and result as below:
+-----------------+---------------------------+------------------------------+
| Environment | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest |
+=================+===========================+==============================+
| Debian 11 (arm) | FAIL | FAIL |
+-----------------+---------------------------+------------------------------+
==== 20 line log output for Debian 11 (arm) (cryptodev_sw_snow3g_autotest): ====
../drivers/net/mlx5/mlx5_flow.c:1031:1: note: previous declaration of 'mlx5_flow_group_set_miss_actions' was here
1031 | mlx5_flow_group_set_miss_actions(struct rte_eth_dev *dev,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/net/mlx5/mlx5_flow.c: In function 'mlx5_flow_group_set_miss_actions':
../drivers/net/mlx5/mlx5_flow.c:9327:53: error: passing argument 3 of 'fops->group_set_miss_actions' from incompatible pointer type [-Werror=incompatible-pointer-types]
9327 | return fops->group_set_miss_actions(dev, group_id, attr, actions, error);
| ^~~~
| |
| const struct rte_flow_group_attr *
../drivers/net/mlx5/mlx5_flow.c:9327:53: note: expected 'const struct rte_flow_group_attr *' but argument is of type 'const struct rte_flow_group_attr *'
../drivers/net/mlx5/mlx5_flow.c: At top level:
../drivers/net/mlx5/mlx5_flow.c:1031:1: error: 'mlx5_flow_group_set_miss_actions' used but never defined [-Werror]
1031 | mlx5_flow_group_set_miss_actions(struct rte_eth_dev *dev,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/net/mlx5/mlx5_flow.c:9312:1: error: 'mlx5_flow_group_set_miss_actions' defined but not used [-Werror=unused-function]
9312 | mlx5_flow_group_set_miss_actions(struct rte_eth_dev *dev,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
[1748/3029] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_rxq.c.o'.
ninja: build stopped: subcommand failed.
==== End log output ====
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27736/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-26 21:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 21:47 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-27 4:03 dpdklab
2023-09-26 23:54 dpdklab
2023-09-26 21:47 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=65135187.170a0220.d2f65.9109SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=tshmilovich@nvidia.com \
/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).