From: kernel test robot <lkp@intel.com>
To: Vlad Buslov <vladbu@nvidia.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Saeed Mahameed <saeedm@nvidia.com>,
Dmytro Linkin <dlinkin@nvidia.com>, Roi Dayan <roid@nvidia.com>
Subject: [linux-next:master 8483/10581] drivers/net/ethernet/mellanox/mlx5/core/en/tc_tun.h:24:29: error: field 'match_level' has incomplete type
Date: Fri, 12 Feb 2021 07:39:52 +0800 [thread overview]
Message-ID: <202102120743.uhHijfLQ-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5806 bytes --]
Hi Vlad,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 671176b0016c80b3943cb5387312c886aba3308d
commit: 0d9f96471493d5483d116c137693f03604332a04 [8483/10581] net/mlx5e: Extract tc tunnel encap/decap code to dedicated file
config: s390-defconfig (attached as .config)
compiler: s390-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=0d9f96471493d5483d116c137693f03604332a04
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 0d9f96471493d5483d116c137693f03604332a04
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=s390
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from drivers/net/ethernet/mellanox/mlx5/core/en_tc.h:40,
from drivers/net/ethernet/mellanox/mlx5/core/en_main.c:45:
>> drivers/net/ethernet/mellanox/mlx5/core/en/tc_tun.h:24:29: error: field 'match_level' has incomplete type
24 | enum mlx5_flow_match_level match_level;
| ^~~~~~~~~~~
drivers/net/ethernet/mellanox/mlx5/core/en/tc_tun.h:27:26: warning: 'struct mlx5e_encap_entry' declared inside parameter list will not be visible outside of this definition or declaration
27 | int (*calc_hlen)(struct mlx5e_encap_entry *e);
| ^~~~~~~~~~~~~~~~~
drivers/net/ethernet/mellanox/mlx5/core/en/tc_tun.h:30:18: warning: 'struct mlx5e_encap_entry' declared inside parameter list will not be visible outside of this definition or declaration
30 | struct mlx5e_encap_entry *e,
| ^~~~~~~~~~~~~~~~~
drivers/net/ethernet/mellanox/mlx5/core/en/tc_tun.h:34:15: warning: 'struct mlx5e_encap_entry' declared inside parameter list will not be visible outside of this definition or declaration
34 | struct mlx5e_encap_entry *e);
| ^~~~~~~~~~~~~~~~~
drivers/net/ethernet/mellanox/mlx5/core/en/tc_tun.h:56:13: warning: 'struct mlx5e_encap_entry' declared inside parameter list will not be visible outside of this definition or declaration
56 | struct mlx5e_encap_entry *e,
| ^~~~~~~~~~~~~~~~~
drivers/net/ethernet/mellanox/mlx5/core/en/tc_tun.h:61:16: warning: 'struct mlx5e_encap_entry' declared inside parameter list will not be visible outside of this definition or declaration
61 | struct mlx5e_encap_entry *e);
| ^~~~~~~~~~~~~~~~~
drivers/net/ethernet/mellanox/mlx5/core/en/tc_tun.h:66:16: warning: 'struct mlx5e_encap_entry' declared inside parameter list will not be visible outside of this definition or declaration
66 | struct mlx5e_encap_entry *e);
| ^~~~~~~~~~~~~~~~~
vim +/match_level +24 drivers/net/ethernet/mellanox/mlx5/core/en/tc_tun.h
101f4de9dd521c Oz Shlomo 2018-12-02 21
d386939a327d2f Yevgeny Kliteynik 2019-04-14 22 struct mlx5e_tc_tunnel {
d386939a327d2f Yevgeny Kliteynik 2019-04-14 23 int tunnel_type;
d386939a327d2f Yevgeny Kliteynik 2019-04-14 @24 enum mlx5_flow_match_level match_level;
d386939a327d2f Yevgeny Kliteynik 2019-04-14 25
d386939a327d2f Yevgeny Kliteynik 2019-04-14 26 bool (*can_offload)(struct mlx5e_priv *priv);
d386939a327d2f Yevgeny Kliteynik 2019-04-14 27 int (*calc_hlen)(struct mlx5e_encap_entry *e);
d386939a327d2f Yevgeny Kliteynik 2019-04-14 28 int (*init_encap_attr)(struct net_device *tunnel_dev,
d386939a327d2f Yevgeny Kliteynik 2019-04-14 29 struct mlx5e_priv *priv,
d386939a327d2f Yevgeny Kliteynik 2019-04-14 30 struct mlx5e_encap_entry *e,
d386939a327d2f Yevgeny Kliteynik 2019-04-14 31 struct netlink_ext_ack *extack);
d386939a327d2f Yevgeny Kliteynik 2019-04-14 32 int (*generate_ip_tun_hdr)(char buf[],
d386939a327d2f Yevgeny Kliteynik 2019-04-14 33 __u8 *ip_proto,
d386939a327d2f Yevgeny Kliteynik 2019-04-14 34 struct mlx5e_encap_entry *e);
d386939a327d2f Yevgeny Kliteynik 2019-04-14 35 int (*parse_udp_ports)(struct mlx5e_priv *priv,
d386939a327d2f Yevgeny Kliteynik 2019-04-14 36 struct mlx5_flow_spec *spec,
f9e30088d20016 Pablo Neira Ayuso 2019-07-09 37 struct flow_cls_offload *f,
d386939a327d2f Yevgeny Kliteynik 2019-04-14 38 void *headers_c,
d386939a327d2f Yevgeny Kliteynik 2019-04-14 39 void *headers_v);
d386939a327d2f Yevgeny Kliteynik 2019-04-14 40 int (*parse_tunnel)(struct mlx5e_priv *priv,
d386939a327d2f Yevgeny Kliteynik 2019-04-14 41 struct mlx5_flow_spec *spec,
f9e30088d20016 Pablo Neira Ayuso 2019-07-09 42 struct flow_cls_offload *f,
d386939a327d2f Yevgeny Kliteynik 2019-04-14 43 void *headers_c,
d386939a327d2f Yevgeny Kliteynik 2019-04-14 44 void *headers_v);
d386939a327d2f Yevgeny Kliteynik 2019-04-14 45 };
d386939a327d2f Yevgeny Kliteynik 2019-04-14 46
:::::: The code at line 24 was first introduced by commit
:::::: d386939a327d2f1c9e918ee843087124eee0efda net/mlx5e: Rearrange tc tunnel code in a modular way
:::::: TO: Yevgeny Kliteynik <kliteyn@mellanox.com>
:::::: CC: Saeed Mahameed <saeedm@mellanox.com>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 19736 bytes --]
reply other threads:[~2021-02-11 23:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202102120743.uhHijfLQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=dlinkin@nvidia.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=roid@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=vladbu@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